From: Breno Leitao <leitao@debian.org>
To: Matthew Wilcox <willy@infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
mm-commits@vger.kernel.org, kent.overstreet@linux.dev,
catalin.marinas@arm.com, bigeasy@linutronix.de, arnd@arndb.de
Subject: Re: + radix-tree-fix-kmemleak-false-positives-on-tree-head-reassignment.patch added to mm-new branch
Date: Mon, 6 Jul 2026 03:41:54 -0700 [thread overview]
Message-ID: <akuFSv7JaXo6M8gx@gmail.com> (raw)
In-Reply-To: <ako1sMPVu4dfQR4K@casper.infradead.org>
Hello Willy,
On Sun, Jul 05, 2026 at 11:45:04AM +0100, Matthew Wilcox wrote:
> > Add a matching kmemleak_transient_leak() stub to the radix tree test
> > harness so the userspace lib/radix-tree.c build keeps building.
>
> Last time this was proposed, the suggestion was that kmemleak needed to
> be fixed.
>
> https://lore.kernel.org/all/aCyI8T2sWlPLEYZ_@arm.com/
My understanding from that thread is that kmemleak could be made more
reliable by explicitly waiting for a rescan before reporting (which it
is a great addition).
This patch explictly tell kmemleak that this object will be temporarily
unreferenced, which is more cooperative.
That said, I believe both approaches. This transient-leak annotation and
Catalin's earlier proposal—can coexist as complementary mechanisms to
reduce kmemleak false positives (which has been my goal, given I run
kmemleak-enabled kernel at some scale)
next prev parent reply other threads:[~2026-07-06 10:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-05 2:12 + radix-tree-fix-kmemleak-false-positives-on-tree-head-reassignment.patch added to mm-new branch Andrew Morton
2026-07-05 10:45 ` Matthew Wilcox
2026-07-05 18:15 ` Andrew Morton
2026-07-06 10:41 ` Breno Leitao [this message]
2026-07-06 11:39 ` Catalin Marinas
2026-07-06 14:53 ` Breno Leitao
2026-07-06 16:25 ` Catalin Marinas
2026-07-06 23:19 ` Catalin Marinas
2026-07-07 11:26 ` Breno Leitao
2026-07-07 14:01 ` Catalin Marinas
-- strict thread matches above, loose matches on Subject: below --
2026-07-05 2:11 Andrew Morton
2026-07-02 22:42 Andrew Morton
2026-07-03 15:26 ` Breno Leitao
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=akuFSv7JaXo6M8gx@gmail.com \
--to=leitao@debian.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=bigeasy@linutronix.de \
--cc=catalin.marinas@arm.com \
--cc=kent.overstreet@linux.dev \
--cc=mm-commits@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.