mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Weilin Tong <tongweilin@linux.alibaba.com>
To: akpm@linux-foundation.org
Cc: catalin.marinas@arm.com, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] mm: kmemleak: avoid long RCU read-side sections in reports
Date: Wed, 11 Nov 2026 15:44:39 +0800	[thread overview]
Message-ID: <20261111074439.316823-1-tongweilin@linux.alibaba.com> (raw)
In-Reply-To: <20261109211709.133122f9f10091f06c4acbc1@linux-foundation.org>

Hi Andrew,

Thanks again for the review. Following up on my earlier reply, I'll
withdraw patch 2 for now while I work on a simpler solution.

Counting visited objects alone still leaves an unbounded RCU section
when walking removed objects. I've tested alternatives, but they add
either substantial read overhead or more cursor and reference-management
complexity than I'd like. I need more time to find a better balance.

Patch 1 fixes an independent cleanup race and has Catalin's Reviewed-by,
so it can be considered separately.

Thanks,
Weilin

      parent reply	other threads:[~2026-11-11  7:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-05  9:52 Weilin Tong
2026-11-05  9:52 ` [PATCH 1/2] mm: kmemleak: serialize disable-time cleanup Weilin Tong
2026-11-10 16:53   ` Catalin Marinas
2026-11-05  9:52 ` [PATCH 2/2] mm: kmemleak: reschedule while reading reports Weilin Tong
2026-11-10  5:17 ` [PATCH 0/2] mm: kmemleak: avoid long RCU read-side sections in reports Andrew Morton
2026-11-10  8:18   ` Weilin Tong
2026-11-11  7:44   ` Weilin Tong [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=20261111074439.316823-1-tongweilin@linux.alibaba.com \
    --to=tongweilin@linux.alibaba.com \
    --cc=akpm@linux-foundation.org \
    --cc=catalin.marinas@arm.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®