linux-kernel - Re: [PATCH] RDMA: 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: <174421797237.375783.9150188033078370474.b4-ty@kernel.org>
Date: Wed, 09 Apr 2025 12:59:32 -0400
From: Leon Romanovsky <leon@...nel.org>
To: Mustafa Ismail <mustafa.ismail@...el.com>, 
 Tatyana Nikolova <tatyana.e.nikolova@...el.com>, 
 Jason Gunthorpe <jgg@...pe.ca>, Christian Benvenuti <benve@...co.com>, 
 Nelson Escobar <neescoba@...co.com>, Bernard Metzler <bmt@...ich.ibm.com>, 
 Thomas Weißschuh <thomas.weissschuh@...utronix.de>
Cc: linux-rdma@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] RDMA: Don't use %pK through printk


On Mon, 07 Apr 2025 10:25:09 +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 looks in atomic contexts.
> 
> [...]

Applied, thanks!

[1/1] RDMA: Don't use %pK through printk
      https://git.kernel.org/rdma/rdma/c/9452c85b58d315

Best regards,
-- 
Leon Romanovsky <leon@...nel.org>