[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a49ccfcd-51ae-eade-8c76-08c4d5d10afc@huawei.com>
Date: Wed, 20 Jul 2022 09:52:26 +0800
From: Baokun Li <libaokun1@...wei.com>
To: Theodore Ts'o <tytso@....edu>, Greg KH <gregkh@...uxfoundation.org>
CC: <stable@...r.kernel.org>, <linux-ext4@...r.kernel.org>,
<adilger.kernel@...ger.ca>, <jack@...e.cz>,
<ritesh.list@...il.com>, <lczerner@...hat.com>,
<enwlinux@...il.com>, <linux-kernel@...r.kernel.org>,
<yi.zhang@...wei.com>, <yebin10@...wei.com>, <yukuai3@...wei.com>,
Hulk Robot <hulkci@...wei.com>,
Baokun Li <libaokun1@...wei.com>
Subject: Re: [PATCH 4.19] ext4: fix race condition between ext4_ioctl_setflags
and ext4_fiemap
在 2022/7/19 22:06, Theodore Ts'o 写道:
> 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
> .
Indeed.
--
With Best Regards,
Baokun Li
Powered by blists - more mailing lists