From: Breno Leitao <leitao@debian.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: 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: Fri, 3 Jul 2026 08:26:36 -0700 [thread overview]
Message-ID: <akfURcWhEWLDjND3@gmail.com> (raw)
In-Reply-To: <20260702224211.8EE791F000E9@smtp.kernel.org>
On Thu, Jul 02, 2026 at 03:42:11PM -0700, Andrew Morton wrote:
>
> The patch titled
> Subject: radix-tree: fix kmemleak false positives on tree head reassignment
> has been added to the -mm mm-new branch. Its filename is
> radix-tree-fix-kmemleak-false-positives-on-tree-head-reassignment.patch
Andrew, would you mind replacing it by v2?
V1 didn't have included kmemleak transient function in userspace headers
(tools/testing/shared/linux/kmemleak.h), thus, userspace test were
failing, as reported by:
https://lore.kernel.org/all/202607031019.AffpLUyg-lkp@intel.com/
V2 was already sent to the list:
https://lore.kernel.org/all/20260703-radix-tree-v2-1-38bb6efb5f6e@debian.org/
Thanks and sorry for the noise,
--breno
next prev parent reply other threads:[~2026-07-03 15:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 22:42 + radix-tree-fix-kmemleak-false-positives-on-tree-head-reassignment.patch added to mm-new branch Andrew Morton
2026-07-03 15:26 ` Breno Leitao [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-07-05 2:11 Andrew Morton
2026-07-05 2:12 Andrew Morton
2026-07-05 10:45 ` Matthew Wilcox
2026-07-05 18:15 ` Andrew Morton
2026-07-06 10:41 ` Breno Leitao
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
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=akfURcWhEWLDjND3@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 \
/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