From: Hyeonggon Yoo <42.hyeyoo@gmail.com>
To: Vernon Yang <vernon2gm@gmail.com>
Cc: akpm@linux-foundation.org, vbabka@suse.cz, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/slub: fix help comment of SLUB_DEBUG[_ON]
Date: Thu, 23 Feb 2023 01:03:49 +0000 [thread overview]
Message-ID: <Y/a7db7v9zJJnX30@localhost> (raw)
In-Reply-To: <20230222232058.66971-1-vernon2gm@gmail.com>
On Thu, Feb 23, 2023 at 07:20:58AM +0800, Vernon Yang wrote:
> Since commit 081248de0a02 ("kset: move /sys/slab to /sys/kernel/slab"),
> the SYSFS path of slab was modified, so fix up the help comment of
> SLUB_DEBUG to use the correct one.
>
> And now the "slub_debug" parameter on boot that is support for more
> fine grained debug control, so fix up help comment of SLUB_DEBUG_ON
> for "no support" to "support".
>
> Signed-off-by: Vernon Yang <vernon2gm@gmail.com>
> ---
> mm/Kconfig.debug | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/mm/Kconfig.debug b/mm/Kconfig.debug
> index fca699ad1fb0..732043bf56c6 100644
> --- a/mm/Kconfig.debug
> +++ b/mm/Kconfig.debug
> @@ -61,8 +61,8 @@ config SLUB_DEBUG
> help
> SLUB has extensive debug support features. Disabling these can
> result in significant savings in code size. This also disables
> - SLUB sysfs support. /sys/slab will not exist and there will be
> - no support for cache validation etc.
> + SLUB sysfs support. /sys/kernel/slab will not exist and there
> + will be no support for cache validation etc.
After commit ab4d5ed5eeda ("slub: Enable sysfs support for !CONFIG_SLUB_DEBUG"),
"Disabling SLUB_DEBUG also disables SLUB sysfs support" is not true anymore.
> config SLUB_DEBUG_ON
> bool "SLUB debugging on by default"
> @@ -73,10 +73,10 @@ config SLUB_DEBUG_ON
> Boot with debugging on by default. SLUB boots by default with
> the runtime debug capabilities switched off. Enabling this is
> equivalent to specifying the "slub_debug" parameter on boot.
> - There is no support for more fine grained debug control like
> - possible with slub_debug=xxx. SLUB debugging may be switched
> - off in a kernel built with CONFIG_SLUB_DEBUG_ON by specifying
> - "slub_debug=-".
> + There is support for more fine grained debug control like
> + possible with slub_debug=xxx, details in Documentation/mm/slub.rst.
> + SLUB debugging may be switched off in a kernel built with
> + CONFIG_SLUB_DEBUG_ON by specifying "slub_debug=-".
I think this is a misunderstanding. SLUB_DEBUG_ON is equivalent to
passing boot parameter slub_debug=FUPZ, and what the help text says is that
"You can enable slub debugging by default using this config option but
there is no support for fine-grained control like what slub_debug
boot parameter provides."
IOW SLUB_DEBUG_ON cannot be used to have same effect as passing
something like slub_debug=F.
>
> config PAGE_OWNER
> bool "Track page owner"
> --
> 2.34.1
>
>
next prev parent reply other threads:[~2023-02-23 1:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 23:20 Vernon Yang
2023-02-23 1:03 ` Hyeonggon Yoo [this message]
2023-03-13 16:26 ` Vlastimil Babka
2023-03-14 6:33 ` Vernon Yang
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=Y/a7db7v9zJJnX30@localhost \
--to=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=vbabka@suse.cz \
--cc=vernon2gm@gmail.com \
/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