From: Oleg Nesterov <oleg@redhat.com>
To: Breno Leitao <leitao@debian.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Andrew Morton <akpm@linux-foundation.org>,
lance.yang@linux.dev, Davidlohr Bueso <dave@stgolabs.net>,
Qian Cai <cai@lca.pw>,
sj@kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org,
kernel-team@meta.com
Subject: Re: [PATCH v3 3/3] mm/kmemleak: stop the per-cpu and struct page scans early too
Date: Tue, 16 Jun 2026 12:07:04 +0200 [thread overview]
Message-ID: <ajEgSI_UiTPU5eIF@redhat.com> (raw)
In-Reply-To: <20260615-kmemleak-stack-resched-v3-3-acecd7d7fd92@debian.org>
On 06/15, Breno Leitao wrote:
>
> #ifdef CONFIG_SMP
> /* per-cpu sections scanning */
> - for_each_possible_cpu(i)
> - scan_large_block(__per_cpu_start + per_cpu_offset(i),
> - __per_cpu_end + per_cpu_offset(i));
> + for_each_possible_cpu(i) {
> + if (scan_large_block(__per_cpu_start + per_cpu_offset(i),
> + __per_cpu_end + per_cpu_offset(i)))
> + break;
> + }
> #endif
The patch looks correct, but...
if scan_large_block() returns true, then
> @@ -1902,6 +1908,7 @@ static void kmemleak_scan(void)
> unsigned long start_pfn = zone->zone_start_pfn;
> unsigned long end_pfn = zone_end_pfn(zone);
> unsigned long pfn;
> + int stop = 0;
>
> for (pfn = start_pfn; pfn < end_pfn; pfn++) {
> struct page *page = pfn_to_online_page(pfn);
> @@ -1918,8 +1925,12 @@ static void kmemleak_scan(void)
> /* only scan if page is in use */
> if (page_count(page) == 0)
> continue;
> - scan_block(page, page + 1, NULL);
> + stop = scan_block(page, page + 1, NULL);
it is pointless to enter this for_each_populated_zone() loop and call
kmemleak_scan_task_stacks() after that?
Not that I think this is bad, just a question...
Oleg.
next prev parent reply other threads:[~2026-06-16 10:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-15 17:49 [PATCH v3 0/3] mm/kmemleak: avoid soft lockup when scanning task stacks Breno Leitao
2026-06-15 17:49 ` [PATCH v3 1/3] " Breno Leitao
2026-06-15 18:24 ` Catalin Marinas
2026-06-15 18:46 ` Davidlohr Bueso
2026-06-16 2:31 ` Lance Yang
2026-06-16 9:48 ` Oleg Nesterov
2026-06-15 17:49 ` [PATCH v3 2/3] mm/kmemleak: stop the task stack scan early when interrupted Breno Leitao
2026-06-15 18:26 ` Catalin Marinas
2026-06-16 9:49 ` Oleg Nesterov
2026-06-15 17:49 ` [PATCH v3 3/3] mm/kmemleak: stop the per-cpu and struct page scans early too Breno Leitao
2026-06-15 18:27 ` Catalin Marinas
2026-06-16 10:07 ` Oleg Nesterov [this message]
2026-06-16 12:46 ` Breno Leitao
2026-06-16 13:10 ` Oleg Nesterov
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=ajEgSI_UiTPU5eIF@redhat.com \
--to=oleg@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=cai@lca.pw \
--cc=catalin.marinas@arm.com \
--cc=dave@stgolabs.net \
--cc=kernel-team@meta.com \
--cc=lance.yang@linux.dev \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sj@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