From: Jeff Layton <jlayton@kernel.org>
To: Kees Cook <kees@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Jakub Kicinski <kuba@kernel.org>,
Eric Dumazet <edumazet@google.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ref_tracker: use %p instead of %px in debugfs dentry name
Date: Thu, 31 Jul 2025 15:01:28 -0400 [thread overview]
Message-ID: <118316e45268be4d98f96f1f1ca0c337e97ea579.camel@kernel.org> (raw)
In-Reply-To: <202507310931.1EE1716CD@keescook>
On Thu, 2025-07-31 at 09:32 -0700, Kees Cook wrote:
> On Thu, Jul 31, 2025 at 07:57:05AM -0400, Jeff Layton wrote:
> > As Kees points out, this is a kernel address leak, and debugging is
> > not a sufficiently good reason to expose the real kernel address.
> >
> > Fixes: 65b584f53611 ("ref_tracker: automatically register a file in debugfs for a ref_tracker_dir")
> > Reported-by: Kees Cook <kees@kernel.org>
> > Closes: https://lore.kernel.org/netdev/202507301603.62E553F93@keescook/
> > Signed-off-by: Jeff Layton <jlayton@kernel.org>
>
> Probably better to use a global u64 counter, but %p can work.
>
I disagree here, again for debugging purposes...
Other kernel debugging code can display a hashed pointer via tracepoint
or printk message, etc. Using the same value in the name here gives us
a mechanism to match that up to the correct debugfs file.
Using a counter would make that harder, and you'd have to store the
counter value in the object (or reach into the dentry -- yuck).
Plus if we _really_ need the physical addresses here in the future, we
can boot with no_hash_pointers and get them.
> Thanks for removing %px!
Thanks for pointing out the problem!
--
Jeff Layton <jlayton@kernel.org>
prev parent reply other threads:[~2025-07-31 19:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-31 11:57 [PATCH] ref_tracker: use %p instead of %px in debugfs dentry name Jeff Layton
2025-07-31 14:13 ` Jakub Kicinski
2025-08-05 20:39 ` Jeff Layton
2025-07-31 16:32 ` Kees Cook
2025-07-31 19:01 ` Jeff Layton [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=118316e45268be4d98f96f1f1ca0c337e97ea579.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=edumazet@google.com \
--cc=kees@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).