mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Kees Cook <kees@kernel.org>, Petr Mladek <pmladek@suse.com>,
	Rasmus Villemoes <linux@rasmusvillemoes.dk>,
	Sergey Senozhatsky <senozhatsky@chromium.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Tycho Andersen <tycho@tycho.pizza>,
	Namhyung Kim <namhyung@kernel.org>
Subject: Re: [PATCH v4 2/2] kallsyms: Don't leak pointers for unresolved symbols
Date: Mon, 19 Oct 2026 14:14:31 +0200	[thread overview]
Message-ID: <20261019121431.nrxar7EO@linutronix.de> (raw)
In-Reply-To: <atX5kxXueI5tjoYa@ashevche-desk.local>

On 2026-10-19 14:05:55 [+0300], Andy Shevchenko wrote:
> On Mon, Oct 19, 2026 at 12:50:25PM +0200, Sebastian Andrzej Siewior wrote:
> > On 2026-10-19 13:34:35 [+0300], Andy Shevchenko wrote:
> > > > +int snprintf_default_pointer(char *buf, unsigned int len, const void *ptr)
> > > > +{
> > > > +	struct printf_spec spec = {
> > > > +		.base = 10,
> > > > +		.precision = -1,
> > > > +		.field_width = -1,
> > > > +	};
> > > 
> > > Isn't it the same as default_dec_spec?
> 
> > Except for .field_width, yes.
> 
> You can update it there. I think in all other cases (I briefly checked, but
> haven't run any smoke test with KUnit) it should be an equivalent.

Okay. So lets give it a try.

> > > > +	unsigned int w;
> > > > +	char *endp;
> > > > +
> > > > +	endp = default_pointer(buf, buf + len, ptr, spec);
> > > > +	w = min_t(unsigned int, len - 1, endp - buf);
> 
> This also won't properly work for len = 0, I assume? So one can't make
> something like kasprintf() on top of this.
> 
> > > May we avoid min_t()?
> > 
> > min() complains about signedness (len unsigned and ptr diff signed).
> > endp is >= buf so it will be unsigned.
> > An alternative would be manual comparison if the buffer size has been
> > exceeded or not and act upon it but this looks simpler.
> 
> It looks simpler, it looks wrong :-)

Could we then exclude len == 0 and keep the remaining bits as-is?

> > > > +	buf[w] = '\0';
> > > > +	return endp - buf;
> > > > +}

Sebastian

  reply	other threads:[~2026-10-19 12:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-19 10:21 [PATCH v4 0/2] vsprintf: Don't leak pointers Sebastian Andrzej Siewior
2026-10-19 10:21 ` [PATCH v4 1/2] vsprintf: Don't leak pointers for %ps without KALLSYMS enabled Sebastian Andrzej Siewior
2026-10-19 15:18   ` Petr Mladek
2026-10-19 10:21 ` [PATCH v4 2/2] kallsyms: Don't leak pointers for unresolved symbols Sebastian Andrzej Siewior
2026-10-19 10:34   ` Andy Shevchenko
2026-10-19 10:50     ` Sebastian Andrzej Siewior
2026-10-19 11:05       ` Andy Shevchenko
2026-10-19 12:14         ` Sebastian Andrzej Siewior [this message]
2026-10-19 15:34   ` Petr Mladek
2026-10-19 15:40     ` 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=20261019121431.nrxar7EO@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=akpm@linux-foundation.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=kees@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=namhyung@kernel.org \
    --cc=pmladek@suse.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®