From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: mm: Don't use %pK through printk
Date: Tue, 18 Feb 2025 10:27:49 +0000 [thread overview]
Message-ID: <Z7RgpaLeIPMQ7kgp@shell.armlinux.org.uk> (raw)
In-Reply-To: <20250217-restricted-pointers-arm-v1-1-aaa0fb22e18c@linutronix.de>
On Mon, Feb 17, 2025 at 08:38:37AM +0100, Thomas Weißschuh wrote:
> Restricted pointers ("%pK") are not meant to be used through printk().
> It can unintentionally expose security sensitive, raw pointer values.
>
> Use regular pointer formatting instead.
... which means that the warning is pointless because no one can debug
it when someone reports that this has fired.
While I get the security issue, changing this is severely harmful to
fixing problems should this warning fire.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2025-02-18 10:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-17 7:38 [PATCH] ARM: mm: Don't use %pK through printk Thomas Weißschuh
2025-02-18 10:27 ` Russell King (Oracle) [this message]
2025-02-18 10:41 ` Thomas Weißschuh
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=Z7RgpaLeIPMQ7kgp@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas.weissschuh@linutronix.de \
/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.