From: Petr Mladek <pmladek@suse.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Kees Cook <kees@kernel.org>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Steven Rostedt <rostedt@goodmis.org>,
Tycho Andersen <tycho@tycho.pizza>
Subject: Re: [PATCH 0/2] vsprintf: Don't leak pointers
Date: Thu, 20 Aug 2026 17:28:25 +0200 [thread overview]
Message-ID: <aocdGcA6TYe5ascV@pathway.suse.cz> (raw)
In-Reply-To: <20260814125647.3e10a3441ca204855b135a5e@linux-foundation.org>
On Fri 2026-08-14 12:56:47, Andrew Morton wrote:
> On Fri, 14 Aug 2026 16:48:52 +0200 Sebastian Andrzej Siewior <bigeasy@linutronix.de> wrote:
>
> > It is possible to leak pointers via %ps without KALLSYMS enabled.
> > With KALLSYMS pointers can be leaked if they can not be resolved.
> >
> > The tiny series has two patches, one for each issue.
> >
>
> Thanks.
>
> fwiw, Sashiko flagged a few possible issues:
> https://sashiko.dev/#/patchset/20260814144854.746840-1-bigeasy@linutronix.de
Sashiko basically complains about that this might make
dump_stack(), panics, and oopses useless on systems without KALLSYMS
which is typical on embedded systems.
IMHO, it is a good point. What about using default_pointer() resp. %p
as the fallback? It would allow to see the pointers with
"no_hash_pointers" kernel parameter.
Best Regards,
Petr
next prev parent reply other threads:[~2026-08-20 15:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 14:48 [PATCH 0/2] vsprintf: Don't leak pointers Sebastian Andrzej Siewior
2026-08-14 14:48 ` [PATCH 1/2] vsprintf: Don't leak pointers for %ps without KALLSYMS enabled Sebastian Andrzej Siewior
2026-08-15 8:58 ` Andy Shevchenko
2026-08-20 14:24 ` Sebastian Andrzej Siewior
2026-08-20 15:40 ` Petr Mladek
2026-08-14 14:48 ` [PATCH 2/2] kallsyms: Don't leak pointers for unresolved symbols Sebastian Andrzej Siewior
2026-08-14 19:08 ` Bradley Morgan
2026-08-14 19:56 ` [PATCH 0/2] vsprintf: Don't leak pointers Andrew Morton
2026-08-20 15:28 ` Petr Mladek [this message]
2026-08-20 15:35 ` Sebastian Andrzej Siewior
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=aocdGcA6TYe5ascV@pathway.suse.cz \
--to=pmladek@suse.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bigeasy@linutronix.de \
--cc=kees@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=tycho@tycho.pizza \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.