All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Petr Mladek <pmladek@suse.com>
Cc: linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.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>,
	Namhyung Kim <namhyung@kernel.org>
Subject: Re: [PATCH v5 2/2] kallsyms: Don't leak pointers for unresolved symbols
Date: Mon, 2 Nov 2026 12:38:40 +0100	[thread overview]
Message-ID: <20261102113840.5NM0MeG9@linutronix.de> (raw)
In-Reply-To: <auDKjGxSieq6WAmW@pathway.suse.cz>

On 2026-10-27 17:00:12 [+0100], Petr Mladek wrote:
> Both Sashiko and the intel test robot reports that this triggers:
> 
>    kernel/kallsyms.c: In function '__sprint_symbol':
> >> kernel/kallsyms.c:486:44: warning: format '%p' expects argument of type 'void *', but argument 3 has type 'long unsigned int' [-Wformat=]
>      486 |                 return sprintf(buffer, "0x%p", address - symbol_offset);
>          |                                           ~^   ~~~~~~~~~~~~~~~~~~~~~~~
>          |                                            |           |
>          |                                            void *      long unsigned int
>          |                                           %ld
> 
> So, it should be:
> 
> 		return sprintf(buffer, "0x%p", (void *)(address - symbol_offset));

yes. I do see it locally after double checking. Not sure how I missed
it.

> >  	offset -= symbol_offset;
> 
> Otherwise, it looks good to me. So, with the added cast:
> 
> Reviewed-by: Petr Mladek <pmladek@suse.com>
> 
> There is no need to send v6. I could fix this when pushing.
> I am going to wait few more days for potential feedback.
> I will queue it for 7.5 unless anyone complains in the meantime.

Okay, thank you.

> Best Regards,
> Petr

Sebastian

  reply	other threads:[~2026-11-02 11:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-23 16:46 [PATCH v5 0/2] vsprintf: Don't leak pointers Sebastian Andrzej Siewior
2026-10-23 16:46 ` [PATCH v5 1/2] vsprintf: Don't leak pointers for %ps without KALLSYMS enabled Sebastian Andrzej Siewior
2026-10-23 16:46 ` [PATCH v5 2/2] kallsyms: Don't leak pointers for unresolved symbols Sebastian Andrzej Siewior
2026-10-24  2:13   ` kernel test robot
2026-10-24 10:07   ` Andy Shevchenko
2026-10-24 16:10     ` Sebastian Andrzej Siewior
2026-10-25 14:51       ` Andy Shevchenko
2026-10-27 16:00   ` Petr Mladek
2026-11-02 11:38     ` Sebastian Andrzej Siewior [this message]
2026-11-03 14:10 ` [PATCH v5 0/2] vsprintf: Don't leak pointers Petr Mladek
2026-11-03 15:45   ` 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=20261102113840.5NM0MeG9@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 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.