summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/stackcollapse.py
diff options
context:
space:
mode:
authorThomas Weißschuh <thomas.weissschuh@linutronix.de>2025-03-10 18:38:23 +0300
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2025-03-14 11:17:29 +0300
commitf4aa6caa8b420bcc0813fccecbc35f43203297df (patch)
tree03fb2a86e7482b2dff3d7695e2567b5b1df2f0dc /tools/perf/scripts/python/stackcollapse.py
parent8c75f3e6a433d92084ad4e78b029ae680865420f (diff)
downloadlinux-f4aa6caa8b420bcc0813fccecbc35f43203297df.tar.xz
usb: core: Don't use %pK through printk
This is a revert of commit 2f964780c03b ("USB: core: replace %p with %pK"). When the formatting was changed from %p to %pK that was a security improvement, as %p would leak raw pointer values to the kernel log. Since commit ad67b74d2469 ("printk: hash addresses printed with %p") the regular %p has been improved to avoid this issue. On the other hand, restricted pointers ("%pK") were never meant to be used through printk(). They can unintentionally still leak raw pointers or acquire sleeping looks in atomic contexts. Switch back to regular %p again. Link: https://lore.kernel.org/lkml/20250113171731-dc10e3c1-da64-4af0-b767-7c7070468023@linutronix.de/ Signed-off-by: Thomas Weißschuh <thomas.weissschuh@linutronix.de> Link: https://lore.kernel.org/r/20250310-restricted-pointers-usb-v2-1-a7598e2d47d1@linutronix.de Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions