mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Breno Leitao <leitao@debian.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	 David Hildenbrand <david@kernel.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	 kernel-team@meta.com
Subject: Re: [PATCH v2] mm: kmemleak: scan modified objects as soon as they are grayed
Date: Mon, 2 Nov 2026 03:06:05 -0800	[thread overview]
Message-ID: <auhuASGI3Y30ERpn@gmail.com> (raw)
In-Reply-To: <20261030120625.c2aa64b3e6378a2e78f2f676@linux-foundation.org>

Hello Andrew,

On Fri, Oct 30, 2026 at 12:06:25PM -0700, Andrew Morton wrote:
> On Fri, 30 Oct 2026 11:31:10 -0700 Breno Leitao <leitao@debian.org> wrote:
> >
> > Scanning the gray list after every grayed object made a full scan 41%
> > slower (1.72s -> 2.42s, arm64 guest with lockdep) when the pass grays a
> > million objects that do not point to each other. Scanning it at most
> > once a jiffy keeps that at the baseline, leaves idle, file storm and
> > mmap churn workloads unchanged, and still removes the false positives
> > at HZ=100.
> 
> Thanks.  I'm thinking
> 
> Fixes: 04609ccc40c4 ("kmemleak: Reduce the false positives by checking for modified objects")
> cc:stable
> 
> Agreed?

Maybe, I think this is a another new way to fix false positives rather
than a issue/bug fix itself, so, I would keep the Fixes:/Stable: tags
out of this one.

Thanks for asking,
--breno

      reply	other threads:[~2026-11-02 11:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-30 18:31 Breno Leitao
2026-10-30 19:06 ` Andrew Morton
2026-11-02 11:06   ` Breno Leitao [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=auhuASGI3Y30ERpn@gmail.com \
    --to=leitao@debian.org \
    --cc=akpm@linux-foundation.org \
    --cc=catalin.marinas@arm.com \
    --cc=david@kernel.org \
    --cc=kernel-team@meta.com \
    --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
all inboxes | Powered by JetHome®