From: Greg KH <gregkh@linuxfoundation.org>
To: Theodore Ts'o <tytso@mit.edu>
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 21:14:32 +0200 [thread overview]
Message-ID: <YtcCmILbA9mTh4Au@kroah.com> (raw)
In-Reply-To: <Ytb+ji56S/de/5Rm@mit.edu>
On Tue, Jul 19, 2022 at 02:57:18PM -0400, Theodore Ts'o wrote:
> P.S. If we go down this path, Greg K-H may also insist on getting the
> bug fix to the 5.4 LTS kernel, so that a bug isn't just fixed in 4.19
> LTS but not 5.4 LTS. In which case, the same requirement of running
> "-c ext4/all -g auto" and showing that there are no test regressions
> is going to be a requirement for 5.4 LTS as well.
Yes, if this issue is also in 5.4 or any newer kernels, it HAS to be
fixed there at the same time, or before, as we can not have anyone
upgrading from an older kernel to a newer one and having a regression.
thanks,
greg k-h
next prev parent reply other threads:[~2022-07-19 19:14 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 [this message]
2022-07-20 2:04 ` Baokun Li
2022-07-19 14:06 ` Theodore Ts'o
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=YtcCmILbA9mTh4Au@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=adilger.kernel@dilger.ca \
--cc=enwlinux@gmail.com \
--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=tytso@mit.edu \
--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