From: Randy Dunlap <rdunlap@infradead.org>
To: Imran Khan <imran.f.khan@oracle.com>,
glider@google.com, elver@google.com, dvyukov@google.com,
cl@linux.com, penberg@kernel.org, rientjes@google.com,
iamjoonsoo.kim@lge.com, akpm@linux-foundation.org,
vbabka@suse.cz, roman.gushchin@linux.dev, 42.hyeyoo@gmail.com,
corbet@lwn.net
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
kasan-dev@googlegroups.com, linux-mm@kvack.org
Subject: Re: [RFC PATCH] mm/kfence: Introduce kernel parameter for selective usage of kfence.
Date: Wed, 27 Jul 2022 17:00:12 -0700 [thread overview]
Message-ID: <08da326f-3fe4-3342-bce8-bbd94bf8be97@infradead.org> (raw)
In-Reply-To: <20220727234241.1423357-1-imran.f.khan@oracle.com>
Hi--
On 7/27/22 16:42, Imran Khan wrote:
> diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
> index 98e5cb91faab..d66f555df7ba 100644
> --- a/Documentation/admin-guide/kernel-parameters.txt
> +++ b/Documentation/admin-guide/kernel-parameters.txt
> @@ -5553,6 +5553,11 @@
> last alloc / free. For more information see
> Documentation/mm/slub.rst.
>
> + slub_kfence[=slabs][,slabs]]...] [MM, SLUB]
I suppose that 'slabs' are by name?
How can the names be found? via 'slabinfo -l' or 'ls /sys/kernel/slab/' ?
It seems to me that the boot option should be listed as s/slabs/slab/.
I.e., one uses 'comma' to list multiple slabs.
Or is there a way for multiple slabs to be entered without commas?
> + Specifies the slabs for which kfence debug mechanism
> + can be used. For more information about kfence see
> + Documentation/dev-tools/kfence.rst.
> +
thanks.
--
~Randy
next prev parent reply other threads:[~2022-07-28 0:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 23:42 [RFC PATCH] mm/kfence: Introduce kernel parameter for selective usage of kfence Imran Khan
2022-07-28 0:00 ` Randy Dunlap [this message]
2022-07-28 0:51 ` Imran Khan
2022-07-28 7:24 ` Marco Elver
2022-07-31 10:54 ` Imran Khan
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=08da326f-3fe4-3342-bce8-bbd94bf8be97@infradead.org \
--to=rdunlap@infradead.org \
--cc=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=corbet@lwn.net \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=imran.f.khan@oracle.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=vbabka@suse.cz \
/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;
as well as URLs for NNTP newsgroup(s).