From: Catalin Marinas <catalin.marinas@arm.com>
To: Breno Leitao <leitao@debian.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
kernel-team@meta.com
Subject: Re: [PATCH] mm: kmemleak: default min_unref_scans to 2 for verbose auto-scan
Date: Mon, 3 Aug 2026 14:44:22 +0100 [thread overview]
Message-ID: <anCbNtFjv9B16gcG@arm.com> (raw)
In-Reply-To: <anCagP6JDQG9w71j@arm.com>
On Mon, Aug 03, 2026 at 02:41:20PM +0100, Catalin Marinas wrote:
> On Thu, Jul 30, 2026 at 07:31:21AM -0700, Breno Leitao wrote:
> > min_unref_scans defers reporting an object as leaked until it has stayed
> > unreferenced for that many consecutive scans, filtering out objects that
> > are only transiently unreferenced during a scan.
> >
> > It defaults to 1, which reports on the first unreferenced scan.
> >
> > When CONFIG_DEBUG_KMEMLEAK_AUTO_SCAN and CONFIG_DEBUG_KMEMLEAK_VERBOSE are
> > both enabled, the scan thread runs periodically and the user has opted into
> > detailed leak reporting, so a second confirming scan happens on its own.
> >
> > Default min_unref_scans to 2 in that configuration to suppress transient
> > false positives.
> >
> > Keep the default at 1 otherwise, where a manually triggered scan is
> > expected to report immediately. The value stays writable through the module
> > parameter.
> >
> > Signed-off-by: Breno Leitao <leitao@debian.org>
>
> Acked-by: Catalin Marinas <catalin.marinas@arm.com>
Ah, I noticed there's a v2. Ignore this one.
--
Catalin
prev parent reply other threads:[~2026-08-03 13:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 14:31 [PATCH] mm: kmemleak: default min_unref_scans to 2 for verbose auto-scan Breno Leitao
2026-08-03 13:41 ` Catalin Marinas
2026-08-03 13:44 ` Catalin Marinas [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=anCbNtFjv9B16gcG@arm.com \
--to=catalin.marinas@arm.com \
--cc=akpm@linux-foundation.org \
--cc=kernel-team@meta.com \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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