Re: [PATCH] ovl: Allow changing default fsync_mode

Yafang Shao <[email protected]> Wed, 24 Jun 2026 11:28:36 +0800
Newsgroups org.kernel.vger.linux-unionfs,org.kernel.vger.linux-fsdevel,org.kernel.vger.linux-kernel
Message-ID <CALOAHbDrWR0eRF9gST14Vm3xOimDZ=iLdn0zRFiF7OeBtqOD=A@mail.gmail.com>
On Wed, Jun 24, 2026 at 11:17 AM Gao Xiang <[email protected]> wrote:
>
> Hi,
>
> On 2026/6/24 10:30, Yafang Shao wrote:
> > On Wed, Jun 24, 2026 at 10:28 AM Gao Xiang <[email protected]> wrote:
> >>
> >>
> >>
> >> On 2026/6/24 10:09, Yafang Shao wrote:
> >>> On Tue, Jun 23, 2026 at 10:52 PM Amir Goldstein <[email protected]> wrote:
> >>>>
> >>>> On Tue, Jun 23, 2026 at 3:47 PM Gao Xiang <[email protected]> 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 ;)
>
> The whole thread is:
> https://lore.kernel.org/linux-unionfs/[email protected]/T/#u
>
> Personally, I feel offensive due to Yafang's expression
> written above.  I keep maintain my replies in technical
> discussion, but the replies above already include the
> following words:
>
> "No wonder containerd is getting harder and harder to use ;)"
>
> "Please do your homework."
>
> "Again, pls do your homework."
>
> and the emotional texts `;)` make me feel uneasy over the
> time,
>
> especially the final words "I'll just go ahead and redirect
> you to /dev/null ;)"
>
> So I write an email as a public report to the CoC since I'm
> not sure how to proceed to comment the community patches
> because I could get offence as a result.

I believe you could learn a thing or two from Amir about how to
comment on others' patches ;)

-- 
Regards
Yafang