From: "Li,Rongqing" <lirongqing@baidu.com>
To: "Vlastimil Babka (SUSE)" <vbabka@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Harry Yoo <harry@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Hao Li <hao.li@linux.dev>, Christoph Lameter <cl@gentwo.org>,
David Rientjes <rientjes@google.com>,
Roman Gushchin <roman.gushchin@linux.dev>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Cc: Matthew Wilcox <willy@infradead.org>, Usama Arif <usama.arif@linux.dev>
Subject: 答复: [外部邮件] Re: [PATCH][v2] mm/mempool: Untangle CONFIG_SLUB_DEBUG_ON abuse and switch to static key
Date: Tue, 2 Jun 2026 09:26:58 +0000 [thread overview]
Message-ID: <fade35b47d62413ea01379781004c549@baidu.com> (raw)
In-Reply-To: <3674d3a8-b30e-4bf1-a4ab-0f82c494d131@kernel.org>
> On 6/2/26 08:21, lirongqing wrote:
> > From: Li RongQing <lirongqing@baidu.com>
> >
> > The mempool subsystem historically wrapped its debugging logic inside
> > an merely defines compile-time defaults for SLUB and caused two flaws:
> >
> > 1. On production kernels where CONFIG_SLUB_DEBUG=y but
> > CONFIG_SLUB_DEBUG_ON=n, mempool debugging was completely
> compiled out
> > at compile time.
> > 2. On kernels with CONFIG_SLUB_DEBUG_ON=y, mempool debugging stayed
> active
> > even if a user explicitly disabled slub debugging at boot time.
> >
> > Clean up this mess by removing the #ifdef and switching to a runtime
> > static key (mempool_debug_enabled), allowing mempool debugging to be
> > toggled cleanly via its own boot parameter.
> >
> > Suggested-by: Vlastimil Babka (SUSE) <vbabka@kernel.org>
> > Signed-off-by: Li RongQing <lirongqing@baidu.com>
> > Cc: Vlastimil Babka <vbabka@kernel.org>
> > Cc: Harry Yoo <harry@kernel.org>
> > Cc: Andrew Morton <akpm@linux-foundation.org>
> > Cc: Hao Li <hao.li@linux.dev>
> > Cc: Christoph Lameter <cl@gentwo.org>
> > Cc: David Rientjes <rientjes@google.com>
> > Cc: Roman Gushchin <roman.gushchin@linux.dev>
> > Cc: Matthew Wilcox <willy@infradead.org>
> > Cc: Usama Arif <usama.arif@linux.dev>
> > ---
> > Diff with v1:
> > Rewrite commit message, change early_param to __setup
> >
> > Documentation/admin-guide/kernel-parameters.txt | 5 ++++
> > mm/mempool.c | 32
> ++++++++++++++++++-------
> > 2 files changed, 28 insertions(+), 9 deletions(-)
> >
> > diff --git a/Documentation/admin-guide/kernel-parameters.txt
> > b/Documentation/admin-guide/kernel-parameters.txt
> > index 642659b..89b5994 100644
> > --- a/Documentation/admin-guide/kernel-parameters.txt
> > +++ b/Documentation/admin-guide/kernel-parameters.txt
> > @@ -3980,6 +3980,11 @@ Kernel parameters
> > Note that even when enabled, there are a few cases where
> > the feature is not effective.
> >
> > + mempool_debug [MM]
> > + Enable mempool debugging. This enables element
> > + poison checking when freeing elements back to the
> > + pool. Useful for debugging mempool corruption.
> > +
> > memtest= [KNL,X86,ARM,M68K,PPC,RISCV,EARLY] Enable memtest
> > Format: <integer>
> > default : 0 <disable>
> > diff --git a/mm/mempool.c b/mm/mempool.c index db23e0e..71e4b54
> 100644
> > --- a/mm/mempool.c
> > +++ b/mm/mempool.c
> > @@ -16,11 +16,28 @@
> > #include <linux/export.h>
> > #include <linux/mempool.h>
> > #include <linux/writeback.h>
> > +#include <linux/static_key.h>
> > +#include <linux/init.h>
> > #include "slab.h"
> >
> > static DECLARE_FAULT_ATTR(fail_mempool_alloc);
> > static DECLARE_FAULT_ATTR(fail_mempool_alloc_bulk);
> >
> > +/*
> > + * Debugging support for mempool using static key.
> > + *
> > + * This allows enabling mempool debug at boot time via:
> > + * mempool_debug
> > + */
> > +static DEFINE_STATIC_KEY_FALSE(mempool_debug_enabled);
> > +
> > +static int __init mempool_debug_setup(char *str) {
> > + static_branch_enable(&mempool_debug_enabled);
> > + return 1;
> > +}
> > +__setup("mempool_debug", mempool_debug_setup);
> > +
> > static int __init mempool_faul_inject_init(void) {
> > int error;
> > @@ -37,7 +54,6 @@ static int __init mempool_faul_inject_init(void) }
> > late_initcall(mempool_faul_inject_init);
> >
> > -#ifdef CONFIG_SLUB_DEBUG_ON
> > static void poison_error(struct mempool *pool, void *element, size_t size,
> > size_t byte)
> > {
> > @@ -73,6 +89,9 @@ static void __check_element(struct mempool *pool,
> > void *element, size_t size)
> >
> > static void check_element(struct mempool *pool, void *element) {
> > + if (!static_branch_unlikely(&mempool_debug_enabled))
> > + return;
>
> With static keys it's better to have the check in the caller of check_element so
> we skip over that call if it's disabled, and not do a call that immediately
> returns. Since there's a single caller, there's no need for an extra inline
> wrapper.
>
Ok, I will change it in next version
Thanks
[Li,Rongqing]
> > +
> > /* Skip checking: KASAN might save its metadata in the element. */
> > if (kasan_enabled())
> > return;
> > @@ -112,6 +131,9 @@ static void __poison_element(void *element, size_t
> > size)
> >
> > static void poison_element(struct mempool *pool, void *element) {
> > + if (!static_branch_unlikely(&mempool_debug_enabled))
> > + return;
>
> Ditto.
>
> > +
> > /* Skip poisoning: KASAN might save its metadata in the element. */
> > if (kasan_enabled())
> > return;
> > @@ -140,14 +162,6 @@ static void poison_element(struct mempool
> *pool,
> > void *element) #endif
> > }
> > }
> > -#else /* CONFIG_SLUB_DEBUG_ON */
> > -static inline void check_element(struct mempool *pool, void *element)
> > -{ -} -static inline void poison_element(struct mempool *pool, void
> > *element) -{ -} -#endif /* CONFIG_SLUB_DEBUG_ON */
> >
> > static __always_inline bool kasan_poison_element(struct mempool *pool,
> > void *element)
prev parent reply other threads:[~2026-06-02 9:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 6:21 [PATCH][v2] mm/mempool: Untangle CONFIG_SLUB_DEBUG_ON abuse and switch to static key lirongqing
2026-06-02 9:10 ` Vlastimil Babka (SUSE)
2026-06-02 9:26 ` Li,Rongqing [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=fade35b47d62413ea01379781004c549@baidu.com \
--to=lirongqing@baidu.com \
--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=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=skhan@linuxfoundation.org \
--cc=usama.arif@linux.dev \
--cc=vbabka@kernel.org \
--cc=willy@infradead.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