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: <831d8af6-5bb0-4869-b9a5-6a4442ec8d67@flourine.local>
Date: Wed, 29 Oct 2025 11:14:27 +0100
From: Daniel Wagner <dwagner@...e.de>
To: Christoph Hellwig <hch@....de>
Cc: Daniel Wagner <wagi@...nel.org>, Keith Busch <kbusch@...nel.org>, 
	John Meneghini <jmeneghi@...hat.com>, Bryan Gurney <bgurney@...hat.com>, 
	linux-nvme@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] nvme: drop bogus nid quirk for multipath devices which
 passed id test

On Wed, Oct 29, 2025 at 10:59:07AM +0100, Christoph Hellwig wrote:
> The problem is that there is no such thing as a sanity check.  Otherwise
> life would be easy.  But I really can't believe that Dell is incompetent
> enough to not leave a mark of their OEM Firmware version anywhere.

Got it. Sure, there are version strings though not really 'stable' as
Hannes told me. Maybe there is a way to filter these out. But isn't this
what the command line idea overwrite feature is?

John, did you have some progress with this?

The sad thing is that the Intel device needs the quirk. If the Dell
device just would use it's own IDs...

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ