dmaengine: stm32: Don't use %pK through printk
authorThomas Weißschuh <thomas.weissschuh@linutronix.de>
Wed, 18 Jun 2025 07:43:34 +0000 (09:43 +0200)
committerVinod Koul <vkoul@kernel.org>
Thu, 26 Jun 2025 22:27:55 +0000 (15:27 -0700)
commit6e6d3c6f0ef235a95c25385b2dad98e8ad6223eb
tree6ae326d11425e9ac4b89927901a9e1ac58fee91e
parente19bdbaa31082b43dab1d936e20efcebc30aa73d
dmaengine: stm32: 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>
Reviewed-by: Amelie Delaunay <amelie.delaunay@foss.st.com>
Link: https://lore.kernel.org/r/20250618-restricted-pointers-dma-v2-1-bc39dafc201d@linutronix.de
Signed-off-by: Vinod Koul <vkoul@kernel.org>
drivers/dma/stm32/stm32-dma.c
drivers/dma/stm32/stm32-dma3.c
drivers/dma/stm32/stm32-mdma.c