From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Baokun Li <libaokun1@huawei.com>
Cc: stable@vger.kernel.org, stable-commits@vger.kernel.org,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Yang Erkun <yangerkun@huawei.com>
Subject: Re: Patch "Revert "mm/filemap: avoid buffered read/write race to read inconsistent data"" has been added to the 6.6-stable tree
Date: Mon, 14 Oct 2024 11:33:19 +0200 [thread overview]
Message-ID: <2024101411-easing-footprint-d770@gregkh> (raw)
In-Reply-To: <886a1275-814d-4be9-9339-5118c7dc2819@huawei.com>
On Fri, Oct 11, 2024 at 09:44:42AM +0800, Baokun Li wrote:
> On 2024/10/11 8:17, Sasha Levin wrote:
> > This is a note to let you know that I've just added the patch titled
> >
> > Revert "mm/filemap: avoid buffered read/write race to read inconsistent data"
> >
> > to the 6.6-stable tree which can be found at:
> > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> >
> > The filename of the patch is:
> > revert-mm-filemap-avoid-buffered-read-write-race-to-.patch
> > and it can be found in the queue-6.6 subdirectory.
> >
> > If you, or anyone else, feels it should not be added to the stable tree,
> > please let <stable@vger.kernel.org> know about it.
> >
> Hi Sasha,
>
> The current patch is a cleanup after adding
> smp_load_acquire/store_release() to i_size_read/write().
>
> In my opinion stable versions continue to use smp_rmb just fine,
> no need to backport the current patch to stable.
>
> In addition, the current patch belongs to a patch set:
>
> https://lore.kernel.org/all/20240124142857.4146716-1-libaokun1@huawei.com/
>
> If the current patch does need to be backported to stable, then the
> entire patch set needs to be backported or problems will be introduced.
>
> All the patches in the patch set are listed below:
>
> d8f899d13d72 ("fs: make the i_size_read/write helpers be
> smp_load_acquire/store_release()")
> 4b944f8ef996 ("Revert "mm/filemap: avoid buffered read/write race to read
> inconsistent data"")
> ad72872eb3ae ("asm-generic: remove extra type checking in acquire/release
> for non-SMP case")
Ok, now dropped, thanks
greg k-h
prev parent reply other threads:[~2024-10-14 9:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241011001701.1645057-1-sashal@kernel.org>
2024-10-11 1:44 ` Patch "Revert "mm/filemap: avoid buffered read/write race to read inconsistent data"" has been added to the 6.6-stable tree Baokun Li
2024-10-14 9:33 ` Greg Kroah-Hartman [this message]
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=2024101411-easing-footprint-d770@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=libaokun1@huawei.com \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=willy@infradead.org \
--cc=yangerkun@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