linux-kernel - Re: [PATCH] scsi: 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: <175038845869.1665414.6330710566460469653.b4-ty@oracle.com>
Date: Thu, 19 Jun 2025 23:18:38 -0400
From: "Martin K. Petersen" <martin.petersen@...cle.com>
To: Yihang Li <liyihang9@...wei.com>,
        "James E.J. Bottomley" <James.Bottomley@...senPartnership.com>,
        Thomas Weißschuh <thomas.weissschuh@...utronix.de>
Cc: "Martin K . Petersen" <martin.petersen@...cle.com>,
        linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] scsi: Don't use %pK through printk

On Wed, 11 Jun 2025 11:58: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 to 6.17/scsi-queue, thanks!

[1/1] scsi: Don't use %pK through printk
      https://git.kernel.org/mkp/scsi/c/76549adb4260

-- 
Martin K. Petersen	Oracle Linux Engineering