Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <[email protected]>:
On Mon, 11 Aug 2025 11:43:17 +0200 you 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.
>
> [...]
Here is the summary with links:
- [net-next,v5,1/2] ice: Don't use %pK through printk or tracepoints
https://git.kernel.org/netdev/net-next/c/66ceb45b7d7e
- [net-next,v5,2/2] net/mlx5: Don't use %pK through tracepoints
https://git.kernel.org/netdev/net-next/c/e2068f74b976
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
