linux-kernel - Re: [PATCH 5/5] nvmet-fc: use pr_* print macros instead of dev

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <83e3fc56-9bb3-4372-95e1-3b318c34e26b@flourine.local>
Date: Tue, 28 Oct 2025 16:47:12 +0100
From: Daniel Wagner <dwagner@...e.de>
To: Daniel Wagner <wagi@...nel.org>
Cc: Justin Tee <justin.tee@...adcom.com>, Christoph Hellwig <hch@....de>, 
	Keith Busch <kbusch@...nel.org>, James Smart <james.smart@...adcom.com>, 
	Jens Axboe <axboe@...nel.dk>, linux-nvme@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 5/5] nvmet-fc: use pr_* print macros instead of dev_*

On Tue, Oct 28, 2025 at 04:26:24PM +0100, Daniel Wagner wrote:
> Many of the nvmet-fc log messages cannot print the device used, because
> it's not there yet:
> 
>   (NULL device *): {0:0} Association deleted
> 
> Use the pr_* macros consistently throughout the module and match the
> output of the nvme-fc module.
> 
> Using port:association ids are more useful when debugging what's going
> on, because these match now with the log entries from nvme-fc.

Signed-off-by: Daniel Wagner <wagi@...nel.org>