linux-kernel - Re: [PATCH] remoteproc: Don't use %pK through printk

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <175019584837.714789.5721540056396177513.b4-ty@kernel.org>
Date: Tue, 17 Jun 2025 16:30:52 -0500
From: Bjorn Andersson <andersson@...nel.org>
To: Mathieu Poirier <mathieu.poirier@...aro.org>,
	Patrice Chotard <patrice.chotard@...s.st.com>,
	Thomas Weißschuh <thomas.weissschuh@...utronix.de>
Cc: linux-remoteproc@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] remoteproc: Don't use %pK through printk


On Wed, 11 Jun 2025 12:03: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/1] remoteproc: Don't use %pK through printk
      commit: b0dc512ab7ba177442cfec4a65b2681355d7cb64

Best regards,
-- 
Bjorn Andersson <andersson@...nel.org>