From: Pedro Falcato <pfalcato@suse.de>
To: "Liam R. Howlett" <Liam.Howlett@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
Matthew Wilcox <willy@infradead.org>,
maple-tree@lists.infradead.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] testing/radix-tree/maple: Hack around kfree_rcu not existing
Date: Wed, 6 Aug 2025 11:21:19 +0100 [thread overview]
Message-ID: <diytmqqhv2wd5guvbzuauenr4ucpttlqrcmffecqkdchjyi5bl@x57r6ypqysuw> (raw)
In-Reply-To: <32irwh2uqdg56jrx7mkbcfltu5t4im6l4j44mtq7ylnebtfpt4@te3sbbfuws5q>
On Tue, Aug 05, 2025 at 09:26:47PM -0400, Liam R. Howlett wrote:
> * Pedro Falcato <pfalcato@suse.de> [250718 13:21]:
> > liburcu doesn't have kfree_rcu (or anything similar). Despite that, we
> > can hack around it in a trivial fashion, by adding a wrapper.
> >
> > This wrapper only works for maple_nodes, and not anything else (due to
> > us not being able to know rcu_head offsets in any way), and thus we take
> > advantage of the type checking to avoid future silent breakage.
> >
> > Signed-off-by: Pedro Falcato <pfalcato@suse.de>
>
> Thanks, but shouldn't this be patch 1 so that the testing continues to
> work?
Yeah, that makes sense, I'll re-order these two on a possible v2.
--
Pedro
next prev parent reply other threads:[~2025-08-06 10:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-18 17:21 [PATCH 1/2] maple_tree: Use kfree_rcu in ma_free_rcu Pedro Falcato
2025-07-18 17:21 ` [PATCH 2/2] testing/radix-tree/maple: Hack around kfree_rcu not existing Pedro Falcato
2025-07-18 18:05 ` Sidhartha Kumar
2025-08-06 1:26 ` Liam R. Howlett
2025-08-06 10:21 ` Pedro Falcato [this message]
2025-08-10 14:23 ` Lorenzo Stoakes
2025-08-06 1:25 ` [PATCH 1/2] maple_tree: Use kfree_rcu in ma_free_rcu Liam R. Howlett
2025-08-06 10:20 ` Pedro Falcato
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=diytmqqhv2wd5guvbzuauenr4ucpttlqrcmffecqkdchjyi5bl@x57r6ypqysuw \
--to=pfalcato@suse.de \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=maple-tree@lists.infradead.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