From: Harry Yoo <harry@kernel.org>
To: "Vlastimil Babka (SUSE)" <vbabka@kernel.org>
Cc: Alexey Dobriyan <adobriyan@gmail.com>,
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-mm@kvack.org
Subject: Re: [PATCH] slub: print just the function name in /sys/kernel/slab/*/ctor
Date: Sun, 2 Aug 2026 05:13:48 +0000 [thread overview]
Message-ID: <am7NCCxeg3BsoYSa@dev> (raw)
In-Reply-To: <73d28cff-77f5-4cd6-888e-5dce5ebae459@kernel.org>
On Thu, Jul 30, 2026 at 04:15:26PM +0200, Vlastimil Babka (SUSE) wrote:
> On 7/27/26 07:27, Harry Yoo wrote:
> >
> >
> > On 7/25/26 10:28 PM, Alexey Dobriyan wrote:
> >> Sysfs "ctor" file prints offset/length of the cache's ctor function
> >>
> >> $ sudo cat /sys/kernel/slab/bdev_cache/ctor
> >> init_once+0x0/0x10
> >>
> >> This is not useful:
> >>
> >> Offset will always be 0 because ctor is a function.
> >>
> >> I'm not sure what ctor function size is doing here, it should be in
> >> /proc/kallsyms
> >>
> >> Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
> >> ---
> >
> > I'm not convinced that changing this (without strong justification)
> > after exposing it to sysfs for 10+ years is worth the trouble.
>
> Agreed. It's a pity this was exported in the first place. I can't see a
> benefit for anyone knowing what the function is called. Should have been at
> most a flag whether there's ctor or not.
Agreed.
> But possibly a justification is not to leak the function size, which might
> be theoretically (although unlikely) a hint to some attack.
...but you need to be the owner (root) to read this :P
> Well at least if somebody complains about getting broken, it's trivial to
> revert and we can hear about their usecase.
If we were to experiment with this, we'll change it to print a flag
rather than the ctor's name, right?
> In-tree tools (slabinfo etc) were checked to work properly?
Looks like it doesn't read ctor at all.
Commit a87615b8f9e2 ("SLUB: slabinfo upgrade") added -o/--ops option
that should "Display of ctor / dtor etc.", but it reads "ops" attribute
that has never existed? Bit puzzled.
> >> mm/slub.c | 2 +-
> >> 1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >> --- a/mm/slub.c
> >> +++ b/mm/slub.c
> >> @@ -9149,7 +9149,7 @@ static ssize_t ctor_show(struct kmem_cache *s, char *buf)
> >> {
> >> if (!s->ctor)
> >> return 0;
> >> - return sysfs_emit(buf, "%pS\n", s->ctor);
> >> + return sysfs_emit(buf, "%ps\n", s->ctor);
> >> }
> >> SLAB_ATTR_RO(ctor);
--
Cheers,
Harry / Hyeonggon
next prev parent reply other threads:[~2026-08-02 5:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-25 13:28 [PATCH] slub: print just the function name in /sys/kernel/slab/*/ctor Alexey Dobriyan
2026-07-27 5:27 ` Harry Yoo
2026-07-30 14:15 ` Vlastimil Babka (SUSE)
2026-08-02 5:13 ` Harry Yoo [this message]
2026-07-27 15:52 ` Christoph Lameter (Ampere)
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=am7NCCxeg3BsoYSa@dev \
--to=harry@kernel.org \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cl@gentwo.org \
--cc=hao.li@linux.dev \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--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