linux-kernel - Re: [BUG report] kernel warnings with Samsung 970 EVO 2TB SSD

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: <aKCFjzai3Y0RcGHP@kbusch-mbp>
Date: Sat, 16 Aug 2025 07:20:15 -0600
From: Keith Busch <kbusch@...nel.org>
To: Diederik de Haas <didi.debian@...ow.org>
Cc: linux-nvme@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [BUG report] kernel warnings with Samsung 970 EVO 2TB SSD

On Sat, Aug 16, 2025 at 01:40:44PM +0200, Diederik de Haas wrote:
> Hi,
> 
> I have a Samsung 970 EVO 2TB SSD and I see these kernel warnings:

... 

> I wonder if something can be done to fix those warnings.

Are you talking about this message?

   nvme nvme0: missing or invalid SUBNQN field

You can't do anything about it, but I wouldn't worry about it either.

If you want to see what the driver is reacting to, you can check the
subnqn from command line:

  # nvme id-ctrl /dev/nvme0 | grep subnqn

It'll probably be all zeros. The field has been required by spec, but
the driver tolerates ones that don't implement it. It's just a message
that the device isn't spec compliant, but otherwise perfectly
operational.