From: Matthew Wilcox <willy@infradead.org>
To: Jiayuan Chen <jiayuan.chen@linux.dev>
Cc: linux-mm@kvack.org, Jiayuan Chen <jiayuan.chen@shopee.com>,
syzbot+006987d1be3586e13555@syzkaller.appspotmail.com,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] radix-tree: fix memory leak of intermediate nodes on insert failure
Date: Wed, 25 Feb 2026 14:13:34 +0000 [thread overview]
Message-ID: <aZ8Dju5ythgf31K0@casper.infradead.org> (raw)
In-Reply-To: <20260225071623.41275-1-jiayuan.chen@linux.dev>
On Wed, Feb 25, 2026 at 03:16:18PM +0800, Jiayuan Chen wrote:
> Fix this directly in __radix_tree_create() by tracking the first newly
> linked slot. On allocation failure, sever the partial path with
> rcu_assign_pointer() and free the orphaned nodes via call_rcu() to
> maintain RCU safety for concurrent readers.
I'm not interested in fixing this. Migrate qrtr to use XArray.
prev parent reply other threads:[~2026-02-25 14:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 7:16 Jiayuan Chen
2026-02-25 14:13 ` Matthew Wilcox [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=aZ8Dju5ythgf31K0@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=jiayuan.chen@linux.dev \
--cc=jiayuan.chen@shopee.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=syzbot+006987d1be3586e13555@syzkaller.appspotmail.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