Reference in a new issue

Blame

Copy permalink

Reference in a new issue

Copy permalink

Thomas Weißschuh a259e4eba8 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>		History 2026-03-04 07:20:16 -05:00
..
binder.c	binder: don't use %pK through printk	2026-03-04 07:20:16 -05:00
binder_alloc.c	binder: don't use %pK through printk	2026-03-04 07:20:16 -05:00
binder_alloc.h	binder: fix memory leak in binder_init()	2023-08-16 18:21:59 +02:00
binder_alloc_selftest.c	Revert "android: binder: stop saving a pointer to the VMA"	2023-06-05 09:21:24 +02:00
binder_internal.h	binder: fix max_thread type inconsistency	2024-05-25 16:20:18 +02:00
binder_trace.h	binder: add trace at free transaction.	2020-11-11 08:20:44 +01:00
binderfs.c	binderfs: fix ida_alloc_max() upper bound	2026-02-11 13:35:29 +01:00
Kconfig	treewide: replace '---help---' in Kconfig files with 'help'	2020-06-14 01:57:21 +09:00
Makefile	treewide: Add SPDX license identifier - Makefile/Kconfig	2019-05-21 10:50:46 +02:00