From: Matthew Wilcox <willy@infradead.org>
To: "Christoph Lameter (Ampere)" <cl@gentwo.org>
Cc: lirongqing <lirongqing@baidu.com>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Vlastimil Babka <vbabka@kernel.org>, Harry Yoo <harry@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Hao Li <hao.li@linux.dev>, David Rientjes <rientjes@google.com>,
Roman Gushchin <roman.gushchin@linux.dev>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH] mm/mempool: use static key for boot-time debug enablement
Date: Thu, 28 May 2026 00:09:12 +0100 [thread overview]
Message-ID: <ahd5mIMCnI4DQFn9@casper.infradead.org> (raw)
In-Reply-To: <7f4ec43c-0d9c-190a-0ce5-bc3276b45cb0@gentwo.org>
On Wed, May 27, 2026 at 04:06:18PM -0700, Christoph Lameter (Ampere) wrote:
> On Wed, 27 May 2026, Matthew Wilcox wrote:
>
> > > Please clean this mess up.
> >
> > Isn't that what this patch does?
>
> Its not marked as fixing something nor as addressing the weirdness of
> using CONFIG_SLUB_DEBUG_ON here, A kernel build with CONFIG_SLUB_DEBUG_ON
> can still boot without debugging if a certain kernel command line option
> is given.
Right, but ... if you look at what the patch _does_, doesn't it do what
you're asking for it to do?
next prev parent reply other threads:[~2026-05-27 23:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-27 10:46 lirongqing
2026-05-27 13:03 ` Usama Arif
2026-05-27 16:43 ` Vlastimil Babka (SUSE)
2026-05-28 3:00 ` 答复: [外部邮件] " Li,Rongqing(ACG CCN)
2026-05-28 10:33 ` Usama Arif
2026-05-28 10:50 ` 答复: " Li,Rongqing(ACG CCN)
2026-05-28 12:59 ` Usama Arif
2026-05-29 9:39 ` Vlastimil Babka (SUSE)
2026-06-01 1:28 ` 答复: " Li,Rongqing(ACG CCN)
2026-05-27 20:06 ` Andrew Morton
2026-05-28 7:54 ` Vlastimil Babka (SUSE)
2026-05-27 21:29 ` Christoph Lameter (Ampere)
2026-05-27 22:13 ` Matthew Wilcox
2026-05-27 23:06 ` Christoph Lameter (Ampere)
2026-05-27 23:09 ` Matthew Wilcox [this message]
2026-05-28 7:57 ` 答复: [????] " Li,Rongqing(ACG CCN)
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=ahd5mIMCnI4DQFn9@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=cl@gentwo.org \
--cc=corbet@lwn.net \
--cc=hao.li@linux.dev \
--cc=harry@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lirongqing@baidu.com \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=skhan@linuxfoundation.org \
--cc=vbabka@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
all inboxes | Powered by JetHome®