Linux Overlay Filesystem development
 help / color / mirror / Atom feed
From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: conduct@kernel.org
Cc: Amir Goldstein <amir73il@gmail.com>,
	Christoph Hellwig <hch@lst.de>,
	miklos@szeredi.hu, linux-unionfs@vger.kernel.org,
	fuweid89@gmail.com, Christian Brauner <brauner@kernel.org>,
	Jan Kara <jack@suse.cz>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	derek@mcg.dev, Yafang Shao <laoar.shao@gmail.com>
Subject: Re: [PATCH] ovl: Allow changing default fsync_mode
Date: Wed, 24 Jun 2026 11:17:28 +0800	[thread overview]
Message-ID: <33912eb8-6b2c-40c2-b698-837e3f675d61@linux.alibaba.com> (raw)
In-Reply-To: <CALOAHbC=2AvZYWEUXR9bk2s=2jk_sVK6zimes1H-TK3iFnn_qQ@mail.gmail.com>

Hi,

On 2026/6/24 10:30, Yafang Shao wrote:
> On Wed, Jun 24, 2026 at 10:28 AM Gao Xiang <hsiangkao@linux.alibaba.com> wrote:
>>
>>
>>
>> On 2026/6/24 10:09, Yafang Shao wrote:
>>> On Tue, Jun 23, 2026 at 10:52 PM Amir Goldstein <amir73il@gmail.com> wrote:
>>>>
>>>> On Tue, Jun 23, 2026 at 3:47 PM Gao Xiang <hsiangkao@linux.alibaba.com> 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/20260623084337.54344-1-laoar.shao@gmail.com/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.

Thanks,
Gao Xiang

  reply	other threads:[~2026-06-24  3:17 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-23  8:43 [PATCH] ovl: Allow changing default fsync_mode Yafang Shao
2026-06-23  9:00 ` Gao Xiang
2026-06-23  9:15   ` Yafang Shao
2026-06-23  9:25     ` Gao Xiang
2026-06-23  9:34       ` Yafang Shao
2026-06-23  9:49         ` Gao Xiang
2026-06-23  9:59           ` Yafang Shao
2026-06-23 10:06             ` Gao Xiang
2026-06-23 10:12             ` Gao Xiang
2026-06-23 10:18               ` Yafang Shao
2026-06-23 10:25                 ` Gao Xiang
2026-06-23 11:38                   ` Yafang Shao
2026-06-23 11:59                     ` Gao Xiang
2026-06-23 12:47                       ` Yafang Shao
2026-06-23 13:11                         ` Gao Xiang
2026-06-23 13:19                           ` Yafang Shao
2026-06-23 13:35                             ` Gao Xiang
2026-06-23 13:39                               ` Yafang Shao
2026-06-23 13:42                               ` Christoph Hellwig
2026-06-23 13:46                                 ` Yafang Shao
2026-06-23 13:47                                 ` Gao Xiang
2026-06-23 14:52                                   ` Amir Goldstein
2026-06-24  2:09                                     ` Yafang Shao
2026-06-24  2:28                                       ` Gao Xiang
2026-06-24  2:30                                         ` Yafang Shao
2026-06-24  3:17                                           ` Gao Xiang [this message]
2026-06-24  3:28                                             ` Yafang Shao
2026-06-24  3:36                                               ` Gao Xiang
2026-06-24  3:41                                                 ` Yafang Shao
2026-06-23 13:03             ` Gao Xiang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=33912eb8-6b2c-40c2-b698-837e3f675d61@linux.alibaba.com \
    --to=hsiangkao@linux.alibaba.com \
    --cc=amir73il@gmail.com \
    --cc=brauner@kernel.org \
    --cc=conduct@kernel.org \
    --cc=derek@mcg.dev \
    --cc=fuweid89@gmail.com \
    --cc=hch@lst.de \
    --cc=jack@suse.cz \
    --cc=laoar.shao@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox