All of lore.kernel.org
 help / color / mirror / Atom feed
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 15:10:06 +0200	[thread overview]
Message-ID: <ajFLLnHNm-mUMRaz@redhat.com> (raw)
In-Reply-To: <ajFFTw6natWGsoCy@gmail.com>

Hi Breno,

On 06/16, Breno Leitao wrote:
>
> So I'd rather keep this series as-is and do that optimization as a follow-up
> once it lands, instead of growing a patch that's already been reviewed. Are
> you OK with that?

OK, agreed.

I don't think you need my ack, but FWIW

Reviewed-by: Oleg Nesterov <oleg@redhat.com>


      reply	other threads:[~2026-06-16 13:10 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
2026-06-16 12:46     ` Breno Leitao
2026-06-16 13:10       ` Oleg Nesterov [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=ajFLLnHNm-mUMRaz@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.