From: Andrew Morton <akpm@linux-foundation.org>
To: Matthew Wilcox <willy@infradead.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [GIT PULL] Rare page cache data corruption fix
Date: Sat, 30 Apr 2022 12:22:36 -0700 [thread overview]
Message-ID: <20220430122236.bd8301bcfe11c1f7e40c0517@linux-foundation.org> (raw)
In-Reply-To: <YmMF32RlCn2asAhc@casper.infradead.org>
On Fri, 22 Apr 2022 20:45:35 +0100 Matthew Wilcox <willy@infradead.org> wrote:
> XArray: Two fixes for 5.18
>
> - Fix the test suite build for kmem_cache_alloc_lru()
>
> - Fix a rare race between split and load
This commit did not have a cc:stable. It has a Fixes:, but we've asked
Greg not to backport patches which weren't explicitly cc:stable.
If you think this should be backported I suggest you let Greg know.
prev parent reply other threads:[~2022-04-30 19:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 19:45 Matthew Wilcox
2022-04-22 20:35 ` Linus Torvalds
2022-04-22 20:46 ` pr-tracker-bot
2022-04-30 19:22 ` Andrew Morton [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=20220430122236.bd8301bcfe11c1f7e40c0517@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=torvalds@linux-foundation.org \
--cc=willy@infradead.org \
/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