]> git.ipfire.org Git - thirdparty/linux.git/commit
powerpc: Don't use %pK through printk
authorThomas Weißschuh <thomas.weissschuh@linutronix.de>
Fri, 18 Jul 2025 13:20:25 +0000 (15:20 +0200)
committerMadhavan Srinivasan <maddy@linux.ibm.com>
Tue, 22 Jul 2025 08:51:18 +0000 (14:21 +0530)
commit4bb69d5270df0f78874c93efade580d9550b34a9
tree6208cf6f54fa0f873d7021a835c3845c420074a5
parent75cd37c5f28b85979fd5a65174013010f6b78f27
powerpc: Don't use %pK through printk

In the past %pK was preferable to %p as it would not leak raw pointer
values into the kernel log.
Since commit ad67b74d2469 ("printk: hash addresses printed with %p")
the regular %p has been improved to avoid this issue.
Furthermore, restricted pointers ("%pK") were never meant to be used
through printk(). They can still unintentionally leak raw pointers or
acquire sleeping locks in atomic contexts.

Switch to the regular pointer formatting which is safer and
easier to reason about.

Link: https://lore.kernel.org/lkml/20250113171731-dc10e3c1-da64-4af0-b767-7c7070468023@linutronix.de/
Signed-off-by: Thomas Weißschuh <thomas.weissschuh@linutronix.de>
Reviewed-by: Christophe Leroy <christophe.leroy@csgroup.eu>
Signed-off-by: Madhavan Srinivasan <maddy@linux.ibm.com>
Link: https://patch.msgid.link/20250718-restricted-pointers-powerpc-v2-1-fd7bddd809f3@linutronix.de
arch/powerpc/kernel/eeh_driver.c
arch/powerpc/perf/hv-24x7.c