From: Bert Karwatzki <spasswolf@web.de>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
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>,
Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>,
spasswolf@web.de
Subject: Re: [PATCH hotfix 6.12] maple_tree: correct tree corruption on spanning store
Date: Sat, 05 Oct 2024 15:24:39 +0200 [thread overview]
Message-ID: <2eefc57370d54b70e082edfe69bb98d17fa1b27f.camel@web.de> (raw)
In-Reply-To: <b7eaef5a-016e-46ae-b7e3-2bd16909110e@lucifer.local>
Am Samstag, dem 05.10.2024 um 12:17 +0100 schrieb Lorenzo Stoakes:
> 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 still suspect that this could have been the same error:
https://lkml.org/lkml/2024/8/28/1558
When compiling the kernel without CONFIG_DEBUG_VM maple tree bug results in an
unkillable task, and when trying to kill it first produced the rwsem warning
(and soon after took down the whole system).
But I couldn't reproduce it with the given reproducer, either.
Bert Karwatzki
next prev parent reply other threads:[~2024-10-05 13:24 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
2024-10-05 13:24 ` Bert Karwatzki [this message]
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=2eefc57370d54b70e082edfe69bb98d17fa1b27f.camel@web.de \
--to=spasswolf@web.de \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mikhail.v.gavrilov@gmail.com \
--cc=sidhartha.kumar@oracle.com \
--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