From: "Theodore Ts'o" <tytso@mit.edu>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Baokun Li <libaokun1@huawei.com>,
stable@vger.kernel.org, linux-ext4@vger.kernel.org,
adilger.kernel@dilger.ca, jack@suse.cz, ritesh.list@gmail.com,
lczerner@redhat.com, enwlinux@gmail.com,
linux-kernel@vger.kernel.org, yi.zhang@huawei.com,
yebin10@huawei.com, yukuai3@huawei.com,
Hulk Robot <hulkci@huawei.com>
Subject: Re: [PATCH 4.19] ext4: fix race condition between ext4_ioctl_setflags and ext4_fiemap
Date: Tue, 19 Jul 2022 10:06:04 -0400 [thread overview]
Message-ID: <Yta6THyDwHulhfi5@mit.edu> (raw)
In-Reply-To: <YtaVAWMlxrQNcS34@kroah.com>
On Tue, Jul 19, 2022 at 01:26:57PM +0200, Greg KH wrote:
> On Sat, Jul 16, 2022 at 10:33:30AM +0800, Baokun Li wrote:
> > This problem persists until the patch d3b6f23f7167("ext4: move ext4_fiemap
> > to use iomap framework") is incorporated in v5.7-rc1.
>
> Then why not ask for that change to be added instead?
Switching over to use the iomap framework is a quite invasive change,
which is fraught with danager and potential performance regressions.
So it's really not something that would be considered safe for an LTS
kernel.
As an upstream developer I'd ask why are people trying to use a kernel
as old as 4.19, but RHEL has done more insane things than that. Also,
I know what the answer is, and it's just too depressing for a nice
summer day like this. :-)
- Ted
next prev parent reply other threads:[~2022-07-19 14:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-15 2:39 [PATCH 4.19] ext4: fix race condition between ext4_ioctl_setflags and ext4_fiemap Baokun Li
2022-07-15 14:10 ` Greg KH
2022-07-16 2:33 ` Baokun Li
2022-07-19 11:26 ` Greg KH
2022-07-19 12:15 ` Baokun Li
2022-07-19 12:25 ` Greg KH
2022-07-19 18:57 ` Theodore Ts'o
2022-07-19 19:14 ` Greg KH
2022-07-20 2:04 ` Baokun Li
2022-07-19 14:06 ` Theodore Ts'o [this message]
2022-07-20 1:52 ` Baokun Li
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=Yta6THyDwHulhfi5@mit.edu \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=enwlinux@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hulkci@huawei.com \
--cc=jack@suse.cz \
--cc=lczerner@redhat.com \
--cc=libaokun1@huawei.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ritesh.list@gmail.com \
--cc=stable@vger.kernel.org \
--cc=yebin10@huawei.com \
--cc=yi.zhang@huawei.com \
--cc=yukuai3@huawei.com \
/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