linux-kernel - Re: [PATCH v2] dmaengine: stm32: 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: <175097809000.79884.3200943794194377896.b4-ty@kernel.org>
Date: Thu, 26 Jun 2025 15:48:10 -0700
From: Vinod Koul <vkoul@...nel.org>
To: Amélie Delaunay <amelie.delaunay@...s.st.com>, 
 Maxime Coquelin <mcoquelin.stm32@...il.com>, 
 Alexandre Torgue <alexandre.torgue@...s.st.com>, 
 Thomas Weißschuh <thomas.weissschuh@...utronix.de>
Cc: dmaengine@...r.kernel.org, linux-stm32@...md-mailman.stormreply.com, 
 linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] dmaengine: stm32: Don't use %pK through printk


On Wed, 18 Jun 2025 09:43:34 +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] dmaengine: stm32: Don't use %pK through printk
      commit: 6e6d3c6f0ef235a95c25385b2dad98e8ad6223eb

Best regards,
-- 
~Vinod