summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/git@git.tavy.me:linux-stable.git
diff options
context:
space:
mode:
authorThomas Weißschuh <thomas.weissschuh@linutronix.de>2025-11-06 15:41:57 +0100
committerMark Brown <broonie@kernel.org>2025-11-06 22:55:12 +0000
commit4db4ce15706d6423cc4cac4b05114b0469507bad (patch)
treed7c88ffd42dcc60a680949a2f14d85939e6e7348 /tools/perf/scripts/python/git@git.tavy.me:linux-stable.git
parent47d98d432f19030faf06d4b2ca7fc7493057cae1 (diff)
ASoC: stm32: dfsdm: 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. Signed-off-by: Thomas Weißschuh <thomas.weissschuh@linutronix.de> Link: https://patch.msgid.link/20251106-restricted-pointers-stm-v1-1-7d03eb5020ba@linutronix.de Signed-off-by: Mark Brown <broonie@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/git@git.tavy.me:linux-stable.git')
0 files changed, 0 insertions, 0 deletions