Thomas Weißschuh 21cc92fddf binder: don't use %pK through printk ...

[ Upstream commit 56d2126766 ]

In the past %pK was preferable to %p as it would not leak raw pointer
values into the kernel log. Since commit ad67b74d24 ("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.

There are still a few users of %pK left, but these use it through
seq_file, for which its usage is safe.

Signed-off-by: Thomas Weißschuh <thomas.weissschuh@linutronix.de>
Acked-by: Carlos Llamas <cmllamas@google.com>
Reviewed-by: Alice Ryhl <aliceryhl@google.com>
Link: https://patch.msgid.link/20260107-restricted-pointers-binder-v1-1-181018bf3812@linutronix.de
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>

2026-03-04 07:21:25 -05:00

..

binder_alloc_selftest.c

…

binder_alloc.c

binder: don't use %pK through printk

2026-03-04 07:21:25 -05:00

binder_alloc.h

…

binder_internal.h

…

binder_trace.h

…

binder.c

binder: don't use %pK through printk

2026-03-04 07:21:25 -05:00

binderfs.c

binderfs: fix ida_alloc_max() upper bound

2026-02-11 13:40:18 +01:00

dbitmap.h

…

Kconfig

…

Makefile

…