wifi: ath11k: Don't use %pK through printk
authorThomas Weißschuh <thomas.weissschuh@linutronix.de>
Thu, 17 Apr 2025 13:19:08 +0000 (15:19 +0200)
committerJeff Johnson <jeff.johnson@oss.qualcomm.com>
Thu, 17 Apr 2025 22:49:35 +0000 (15:49 -0700)
commit27c57c84922ef1dc72a2ea3a5427cdbaadc9be44
tree255999275b694f28cfe1138e69ca4a8c904282ea
parent8add2b8d72722b60c749b559db2a2aef6c9def68
wifi: ath11k: 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 looks 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>
Reviewed-by: Aleksandr Loktionov <aleksandr.loktionov@intel.com>
Link: https://patch.msgid.link/20250417-restricted-pointers-ath-v1-2-4e9a04dbe362@linutronix.de
Signed-off-by: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
drivers/net/wireless/ath/ath11k/testmode.c