From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-remoteproc@vger.kernel.org, Bjorn Andersson <andersson@kernel.org>
Subject: Re: [PATCH] remoteproc: Use %p for pointer formatting
Date: Mon, 21 Sep 2026 08:35:09 -0600 [thread overview]
Message-ID: <arFAnRCt-TykCbt3@p14s> (raw)
In-Reply-To: <20260918104628.jqQhAlF-@linutronix.de>
On Fri, Sep 18, 2026 at 12:46:28PM +0200, Sebastian Andrzej Siewior wrote:
> Commit 276ec9934231e ("remoteproc: replace "%p" with "%pK"") introduced
> the %pK in order to not leak kernel pointers.
> Since commit ad67b74d2469d ("printk: hash addresses printed with
> %p") pointers are hashed by default and the behaviour can be controller
> by `hash_pointers' boot argument.
> The policy on %p is to not introduce new ones.
> Removing %pK makes it possible to remove its handling from the library.
>
> I doubt printing the address of struct fw_rsc_hdr with an unknown type
> brings any value. The va is printed already in debug output in other
> places as %p so it makes probably no difference to remove it from
> rproc_carveouts_show().
>
> Use %p instead %pK for rproc_mem_entry::va, remove the address of the
> unknown type.
>
> Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> ---
> drivers/remoteproc/remoteproc_debugfs.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
Applied.
Thanks,
Mathieu
> diff --git a/drivers/remoteproc/remoteproc_debugfs.c b/drivers/remoteproc/remoteproc_debugfs.c
> index b86c1d09c70c0..e8e7b6a3769b8 100644
> --- a/drivers/remoteproc/remoteproc_debugfs.c
> +++ b/drivers/remoteproc/remoteproc_debugfs.c
> @@ -347,8 +347,8 @@ static int rproc_rsc_table_show(struct seq_file *seq, void *p)
> }
> break;
> default:
> - seq_printf(seq, "Unknown resource type found: %d [hdr: %pK]\n",
> - hdr->type, hdr);
> + seq_printf(seq, "Unknown resource type found: %d\n",
> + hdr->type);
> break;
> }
> }
> @@ -367,7 +367,7 @@ static int rproc_carveouts_show(struct seq_file *seq, void *p)
> list_for_each_entry(carveout, &rproc->carveouts, node) {
> seq_puts(seq, "Carveout memory entry:\n");
> seq_printf(seq, "\tName: %s\n", carveout->name);
> - seq_printf(seq, "\tVirtual address: %pK\n", carveout->va);
> + seq_printf(seq, "\tVirtual address: %p\n", carveout->va);
> seq_printf(seq, "\tDMA address: %pad\n", &carveout->dma);
> seq_printf(seq, "\tDevice address: 0x%x\n", carveout->da);
> seq_printf(seq, "\tLength: 0x%zx Bytes\n\n", carveout->len);
> --
> 2.55.0
prev parent reply other threads:[~2026-09-21 14:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 10:46 [PATCH] remoteproc: Use %p for pointer formatting Sebastian Andrzej Siewior
2026-09-21 14:35 ` Mathieu Poirier [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=arFAnRCt-TykCbt3@p14s \
--to=mathieu.poirier@linaro.org \
--cc=andersson@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=linux-remoteproc@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