From: "Liam R. Howlett" <Liam.Howlett@oracle.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: maple-tree@lists.infradead.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, stable@kernel.org,
Suren Baghdasaryan <surenb@google.com>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
Hailong Liu <hailong.liu@oppo.com>,
zhangpeng.00@bytedance.com, Steve Kang <Steve.Kang@unisoc.com>,
Matthew Wilcox <willy@infradead.org>,
Sidhartha Kumar <sidhartha.kumar@oracle.com>
Subject: Re: [PATCH 0/3] Fix MA_STATE_PREALLOC issue
Date: Fri, 20 Jun 2025 14:20:44 -0400 [thread overview]
Message-ID: <7s4xwshwjlsn4e3r4ndxwhh7nz2ztcd4t3zsnjepeludto6j6x@qf7b36dayfvv> (raw)
In-Reply-To: <20250616162404.9f37908a11f5bd46f2362fb9@linux-foundation.org>
* Andrew Morton <akpm@linux-foundation.org> [250616 19:24]:
> On Mon, 16 Jun 2025 14:45:18 -0400 "Liam R. Howlett" <Liam.Howlett@oracle.com> wrote:
>
> > Address the issue of reusing the same maple state for multiple
> > preallocations calls caused by MA_STATE_PREALLOC, and add a test for
> > this use case.
> >
> > Included is a change to the testing code to reduce false positives in
> > the rcu race testing on faster machines.
>
> I split this series into
>
> - a standalone fix for 6.16-rcX and -stable.
>
> - two standalone selftests patches for 6.17-rc1.
>
> Is that OK?
Yes, should be fine.
Thanks for checking.
Liam
prev parent reply other threads:[~2025-06-20 18:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 18:45 Liam R. Howlett
2025-06-16 18:45 ` [PATCH 1/3] testing/raix-tree/maple: Increase readers and reduce delay for faster machines Liam R. Howlett
2025-06-20 15:43 ` Lorenzo Stoakes
2025-06-16 18:45 ` [PATCH 2/3] maple_tree: Fix MA_STATE_PREALLOC flag in mas_preallocate() Liam R. Howlett
2025-06-20 15:50 ` Lorenzo Stoakes
2025-06-16 18:45 ` [PATCH 3/3] tools/testing/radix-tree: Test maple tree chaining mas_preallocate() calls Liam R. Howlett
2025-06-20 15:51 ` Lorenzo Stoakes
2025-06-16 23:24 ` [PATCH 0/3] Fix MA_STATE_PREALLOC issue Andrew Morton
2025-06-20 18:20 ` Liam R. Howlett [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=7s4xwshwjlsn4e3r4ndxwhh7nz2ztcd4t3zsnjepeludto6j6x@qf7b36dayfvv \
--to=liam.howlett@oracle.com \
--cc=Steve.Kang@unisoc.com \
--cc=akpm@linux-foundation.org \
--cc=hailong.liu@oppo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=maple-tree@lists.infradead.org \
--cc=sidhartha.kumar@oracle.com \
--cc=stable@kernel.org \
--cc=surenb@google.com \
--cc=willy@infradead.org \
--cc=zhangpeng.00@bytedance.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