[PATCH ath-next 0/4] wifi: ath: Don't use %pK through printk
Jeff Johnson
jeff.johnson at oss.qualcomm.com
Thu Apr 17 15:57:41 PDT 2025
On Thu, 17 Apr 2025 15:19:06 +0200, Thomas Weißschuh wrote:
> 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.
>
> [...]
Applied, thanks!
[1/4] wifi: ath10k: Don't use %pK through printk
commit: 8add2b8d72722b60c749b559db2a2aef6c9def68
[2/4] wifi: ath11k: Don't use %pK through printk
commit: 27c57c84922ef1dc72a2ea3a5427cdbaadc9be44
[3/4] wifi: ath12k: Don't use %pK through printk
commit: 7e7f948c7d14ab5a6cfb26146a0d4734781903e3
[4/4] wifi: wcn36xx: Don't use %pK through printk
commit: 75f90ba47b2cda7de7a7bc1d099172516f6f96fa
Best regards,
--
Jeff Johnson <jeff.johnson at oss.qualcomm.com>
More information about the ath11k
mailing list