From: Christoph Hellwig <hch@lst.de>
To: hare@kernel.org
Cc: Christoph Hellwig <hch@lst.de>, Keith Busch <kbusch@kernel.org>,
Sagi Grimberg <sagi@grimberg.me>,
wagi@lst.de, linux-nvme@lists.infradead.org
Subject: Re: [PATCH 0/2] nvme: handle partially unique NID value
Date: Mon, 14 Apr 2025 13:19:16 +0200 [thread overview]
Message-ID: <20250414111916.GB13225@lst.de> (raw)
In-Reply-To: <20250414090959.2015-1-hare@kernel.org>
On Mon, Apr 14, 2025 at 11:09:57AM +0200, hare@kernel.org wrote:
> From: Hannes Reinecke <hare@kernel.org>
>
> Hi all,
>
> we have encountered a customer issue where the NID values for additional
> namespaces on the same device are not unique in all cases; the NGUID is,
> but the EUI64 is not. Problem is that prior to commit e2724cb9f0c4 there
> devices worked without a problem, but after that all NIDs are blanked out.
> This results in udev not creating persistent device links anymore and the
> system failing to boot.
These devices are so broken that we absolutely should not support them
You've also received that feedback both in person from me, from Daniel
and from the nvme technical working group. I'm not sure why you insist
resending it instead of telling the OEM that specifically requested this
spec violating behavior from their SSD vendor to stop doing those
broken thing in the many months you have known of this gravely incorrect
indefensible behavior.
next parent reply other threads:[~2025-04-14 11:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250414090959.2015-1-hare@kernel.org>
2025-04-14 11:19 ` Christoph Hellwig [this message]
2025-04-14 11:31 ` [PATCH 0/2] nvme: handle partially unique NID value Hannes Reinecke
2025-04-14 11:41 ` Christoph Hellwig
2025-04-14 11:55 ` Hannes Reinecke
2025-04-14 11:59 ` Christoph Hellwig
2025-04-17 16:56 ` Ballard, Curtis C (HPE Storage)
[not found] ` <CGME20250502082359uscas1p1e2a9858dcc9200ab1d1d863c4495fc0a@uscas1p1.samsung.com>
[not found] ` <eee8de0a44074dd3bfb0fc6ec425b647@samsung.com>
2025-05-02 10:25 ` Christoph Hellwig
[not found] ` <27a99b458f0144fba094726e4f470552@samsung.com>
2025-05-03 3:46 ` Keith Busch
2025-05-05 9:51 ` Javier Gonzalez
2025-05-05 11:11 ` Christoph Hellwig
2025-05-05 13:08 ` Javier Gonzalez
2025-05-05 13:49 ` Laurence Oberman
2025-05-06 7:07 ` Javier Gonzalez
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=20250414111916.GB13225@lst.de \
--to=hch@lst.de \
--cc=hare@kernel.org \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=wagi@lst.de \
/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