Re: [PATCH] ovl: Allow changing default fsync_mode

[Yafang Shao]

On Wed, Jun 24, 2026 at 10:28 AM Gao Xiang <hsiangkao@xxxxxxxxxxxxxxxxx> wrote:
>
>
>
> On 2026/6/24 10:09, Yafang Shao wrote:
> > On Tue, Jun 23, 2026 at 10:52 PM Amir Goldstein <amir73il@xxxxxxxxx> wrote:
> >>
> >> On Tue, Jun 23, 2026 at 3:47 PM Gao Xiang <hsiangkao@xxxxxxxxxxxxxxxxx> wrote:
>
> ...
>
> >
> > Since the "volatile" option has been working fine for over a year
> > across our large fleet of Kubernetes production servers, I submitted
> > this change to upstream. In Kubernetes environments, there is no use
> > case for remounting the workdir to the same directory, so the volatile
> > file won't cause any issues — which is why the "volatile" setting has
> > been working well there.
> That is not an excuse to introduce such new incompatible behavior
> to the linux upstream starting only for your customized fleet and
> bother every single opensource user/application to adapt this
> behavior which uses overlayfs now.
>
> If you insist to work on a breaking change, please gather
> userspace feedback boardly first.
>
> And here I just say you and your employer are lucky since I
> know it's also risky even on the generic kubernate perspective.
> Please just maintain your livepatch downstream, thanks.
>
> No need to reply, and I won't reply this either, it's just
> waste of my time to explain a basic upstream principle again
> and again.

I'll just go ahead and redirect you to /dev/null ;)

-- 
Regards
Yafang