From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Liam R . Howlett" <Liam.Howlett@oracle.com>,
Matthew Wilcox <willy@infradead.org>,
Vlastimil Babka <vbabka@suse.cz>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Sidhartha Kumar <sidhartha.kumar@oracle.com>,
Bert Karwatzki <spasswolf@web.de>,
Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
Subject: Re: [PATCH hotfix 6.12] maple_tree: correct tree corruption on spanning store
Date: Sat, 5 Oct 2024 12:17:53 +0100 [thread overview]
Message-ID: <b7eaef5a-016e-46ae-b7e3-2bd16909110e@lucifer.local> (raw)
In-Reply-To: <20241005064114.42770-1-lorenzo.stoakes@oracle.com>
On Sat, Oct 05, 2024 at 07:41:14AM +0100, Lorenzo Stoakes wrote:
> Writing a data range into a maple tree may involve overwriting a number of
> existing entries that span across more than one node. Doing so invokes a
> 'spanning' store.
>
[snip]
Andrew - just to note that I have intentionally left stable off this, in
order that wre can allow this to stabilise in the 6.12 release candidates.
Up until 6.12 this bug seemed much harder to hit, and as far as I'm aware
we've never had a bug report for it prior to this.
I am confident in the patch for 6.12 as all of the (_numerous_) maple tree
userland tests pass and the kernel is stable with it, but as this is a
such a subtle algorithmic change I think we should be cautious.
As soon as things settle down I will ping stable to get it backported.
Thanks!
next prev parent reply other threads:[~2024-10-05 11:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-05 6:41 Lorenzo Stoakes
2024-10-05 11:17 ` Lorenzo Stoakes [this message]
2024-10-05 13:24 ` Bert Karwatzki
2024-10-05 14:13 ` Lorenzo Stoakes
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=b7eaef5a-016e-46ae-b7e3-2bd16909110e@lucifer.local \
--to=lorenzo.stoakes@oracle.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mikhail.v.gavrilov@gmail.com \
--cc=sidhartha.kumar@oracle.com \
--cc=spasswolf@web.de \
--cc=vbabka@suse.cz \
--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