From: Christoph Hellwig <hch@lst.de>
To: Gao Xiang <hsiangkao@linux.alibaba.com>
Cc: Yafang Shao <laoar.shao@gmail.com>,
miklos@szeredi.hu, amir73il@gmail.com,
linux-unionfs@vger.kernel.org, fuweid89@gmail.com,
Christian Brauner <brauner@kernel.org>,
Christoph Hellwig <hch@lst.de>, Jan Kara <jack@suse.cz>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ovl: Allow changing default fsync_mode
Date: Tue, 23 Jun 2026 15:42:40 +0200 [thread overview]
Message-ID: <20260623134240.GA7980@lst.de> (raw)
In-Reply-To: <b4d43064-7a7d-4d65-b65c-56e80d47ed17@linux.alibaba.com>
I have no idea where this coming from as I can't find an earlier
version in the fsdevel archives. But changing user visible mount
options through konfig options is simply bonkers.
I'd also like to not that the submitter does have a history of crazy
patches including those to support proprietary modules and then
attacking people criticizing those patches, so I can only suggest to
every maintainer to ignore them for their own sanity.
next prev parent reply other threads:[~2026-06-23 13:42 UTC|newest]
Thread overview: 23+ 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 [this message]
2026-06-23 13:46 ` Yafang Shao
2026-06-23 13:47 ` Gao Xiang
2026-06-23 14:52 ` Amir Goldstein
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=20260623134240.GA7980@lst.de \
--to=hch@lst.de \
--cc=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=fuweid89@gmail.com \
--cc=hsiangkao@linux.alibaba.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.