From: Christoph Hellwig <hch@lst.de>
To: Daniel Wagner <dwagner@suse.de>
Cc: Christoph Hellwig <hch@lst.de>, Daniel Wagner <wagi@kernel.org>,
Keith Busch <kbusch@kernel.org>,
John Meneghini <jmeneghi@redhat.com>,
Bryan Gurney <bgurney@redhat.com>,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nvme: drop bogus nid quirk for multipath devices which passed id test
Date: Wed, 29 Oct 2025 14:38:34 +0100 [thread overview]
Message-ID: <20251029133834.GB14596@lst.de> (raw)
In-Reply-To: <831d8af6-5bb0-4869-b9a5-6a4442ec8d67@flourine.local>
On Wed, Oct 29, 2025 at 11:14:27AM +0100, Daniel Wagner wrote:
> 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?
Version isn't optimal, but model numbers often encode model numbers,
and some devices have identifiers in the vendor specific regions of
identify commands.
> 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...
I'm pretty sure they are one and the same device, just with slightly
different firmware versions. It might be that Dell actually reported
the bogus IDs to Intel as part of compliance testing and Intel only
fixed it for them and not the generic firmware build :(
next prev parent reply other threads:[~2025-10-29 13:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-28 12:54 [PATCH] nvme: drop bogus nid quirk for multipath devices which passed id test Daniel Wagner
2025-10-29 7:44 ` Christoph Hellwig
2025-10-29 9:45 ` Daniel Wagner
2025-10-29 9:59 ` Christoph Hellwig
2025-10-29 10:14 ` Daniel Wagner
2025-10-29 13:38 ` Christoph Hellwig [this message]
2025-11-05 7:33 ` Hannes Reinecke
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20251029133834.GB14596@lst.de \
--to=hch@lst.de \
--cc=bgurney@redhat.com \
--cc=dwagner@suse.de \
--cc=jmeneghi@redhat.com \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=wagi@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox