nvme: don't reject probe due to duplicate IDs for single-ported PCIe devices
Christoph Hellwig
maintainerPATCH 1/1 nvme: don't reject probe due to duplicate IDs for single-ported PCIe devices
While duplicate IDs are still very harmful, including the potential to easily see changing devices in /dev/disk/by-id, it turn out they are extremely common for cheap end user NVMe devices.
Relax our check for them for so that it doesn't reject the probe on single-ported PCIe devices, but prints a big warning instead. In doubt we'd still like to see quirk entries to disable the potential for changing supposed stable device identifier links, but this will at least allow users how have two (or more) of these devices to use them without having to manually add a new PCI ID entry with the quirk through sysfs or by patching the kernel.
--- drivers/nvme/host/core.c | 36 +++++++++++++++++++++++++++++++++--- 1 file changed, 33 insertions(+), 3 deletions(-)
drivers/nvme/host/core.c +33 -3
@@ -3431,10 +3431,40 @@ static int nvme_init_ns_head(struct nvme_ns *ns, struct nvme_ns_info *info) ret =nvme_global_check_duplicate_ids (ctrl->subsys, &info->ids);if (ret) { -dev_err (ctrl->device, -"globally duplicate IDs for nsid %d\n" , info->nsid); +/* +* We've found two different namespaces on two different +* subsystems that report the same ID. This is pretty nasty +* for anything that actually requires unique device +* identification. In the kernel we need this for multipathing, +* and in user space the /dev/disk/by-id/ links rely on it. +* +* If the device also claims to be multi-path capable back off +* here now and refuse the probe the second device as this is a +* recipe for data corruption. If not this is probably a +* cheap consumer device if on the PCIe bus, so let the user +* proceed and use the shiny toy, but warn that with changing +* probing order (which due to our async probing could just be +* device taking longer to startup) the other device could show +* up at any time. +*/ nvme_print_device_info (ctrl); -return ret; +if ((ns->ctrl->ops->flags &NVME_F_FABRICS ) ||/* !PCIe */ + ((ns->ctrl->subsys->cmic &NVME_CTRL_CMIC_MULTI_CTRL ) && + info->is_shared)) { +dev_err (ctrl->device, +"ignoring nsid %d because of duplicate IDs\n" , + info->nsid); +return ret; + } + +dev_err (ctrl->device, +"clearing duplicate IDs for nsid %d\n" , info->nsid); +dev_err (ctrl->device, +"use of /dev/disk/by-id/ may cause data corruption\n" ); +memset (&info->ids.nguid,0 ,sizeof (info->ids.nguid)); +memset (&info->ids.uuid,0 ,sizeof (info->ids.uuid)); +memset (&info->ids.eui64,0 ,sizeof (info->ids.eui64)); + ctrl->quirks |=NVME_QUIRK_BOGUS_NID ; }mutex_lock (&ctrl->subsys->lock);
Signature · 1 line
2.39.2
Quoted 11 lines · Christoph Hellwig
While duplicate IDs are still very harmful, including the potential to easily see changing devices in
/dev/disk/by-id, it turn out they are extremely common for cheap end user NVMe devices.Relax our check for them for so that it doesn't reject the probe on single-ported PCIe devices, but prints a big warning instead. In doubt we'd still like to see quirk entries to disable the potential for changing supposed stable device identifier links, but this will at least allow users how have two (or more) of these devices to use them without having to manually add a new PCI ID entry with the quirk through sysfs or by patching the kernel.
Should this go for backport? For the commit 2079f41ec6ffa.
Keith Busch
maintainerQuoted 13 lines · Kanchan Joshi
Quoted 11 lines · Christoph Hellwig
While duplicate IDs are still very harmful, including the potential to easily see changing devices in
/dev/disk/by-id, it turn out they are extremely common for cheap end user NVMe devices.Relax our check for them for so that it doesn't reject the probe on single-ported PCIe devices, but prints a big warning instead. In doubt we'd still like to see quirk entries to disable the potential for changing supposed stable device identifier links, but this will at least allow users how have two (or more) of these devices to use them without having to manually add a new PCI ID entry with the quirk through sysfs or by patching the kernel.
Quoted 1 line
Should this go for backport? For the commit
2079f41ec6ffa.
Is it sufficient if I just append "Cc: stable..." to the commit message?
Jens Axboe
maintainerQuoted 14 lines · Keith Busch
Quoted 13 lines · Kanchan Joshi
Quoted 11 lines · Christoph Hellwig
While duplicate IDs are still very harmful, including the potential to easily see changing devices in
/dev/disk/by-id, it turn out they are extremely common for cheap end user NVMe devices.Relax our check for them for so that it doesn't reject the probe on single-ported PCIe devices, but prints a big warning instead. In doubt we'd still like to see quirk entries to disable the potential for changing supposed stable device identifier links, but this will at least allow users how have two (or more) of these devices to use them without having to manually add a new PCI ID entry with the quirk through sysfs or by patching the kernel.
Quoted 3 lines
Quoted 1 line
Should this go for backport? For the commit
2079f41ec6ffa.Is it sufficient if I just append "Cc: stable..." to the commit message?
You probably want:
and that should do the trick.
Signature · 1 line
Jens Axboe
Keith Busch
maintainerQuoted 6 lines · Jens Axboe
You probably want:
Fixes 2079f41ec6ff ("nvme: check that EUI/GUID/UUID are globally unique")and that should do the trick.
Done, pushed to nvme-6.5. I'll send a new pull request before end-of-day.
Quoted 56 lines · Christoph Hellwig
While duplicate IDs are still very harmful, including the potential to easily see changing devices in
/dev/disk/by-id, it turn out they are extremely common for cheap end user NVMe devices.Relax our check for them for so that it doesn't reject the probe on single-ported PCIe devices, but prints a big warning instead. In doubt we'd still like to see quirk entries to disable the potential for changing supposed stable device identifier links, but this will at least allow users how have two (or more) of these devices to use them without having to manually add a new PCI ID entry with the quirk through sysfs or by patching the kernel.
Co-developed-by Sagi Grimberg <[email protected]>Signed-off-by Christoph Hellwig <[email protected]>--- drivers/nvme/host/core.c | 36 +++++++++++++++++++++++++++++++++--- 1 file changed, 33 insertions(+), 3 deletions(-)drivers/nvme/host/core.c +26
-3@@ -3431,10 +3431,40 @@ static int nvme_init_ns_head(struct nvme_ns *ns, struct nvme_ns_info *info) ret =nvme_global_check_duplicate_ids (ctrl->subsys, &info->ids);if (ret) { -dev_err (ctrl->device, -"globally duplicate IDs for nsid %d\n" , info->nsid); +/* +* We've found two different namespaces on two different +* subsystems that report the same ID. This is pretty nasty +* for anything that actually requires unique device +* identification. In the kernel we need this for multipathing, +* and in user space the /dev/disk/by-id/ links rely on it. +* +* If the device also claims to be multi-path capable back off +* here now and refuse the probe the second device as this is a +* recipe for data corruption. If not this is probably a +* cheap consumer device if on the PCIe bus, so let the user +* proceed and use the shiny toy, but warn that with changing +* probing order (which due to our async probing could just be +* device taking longer to startup) the other device could show +* up at any time. +*/ nvme_print_device_info (ctrl); -return ret; +if ((ns->ctrl->ops->flags &NVME_F_FABRICS ) ||/* !PCIe */ + ((ns->ctrl->subsys->cmic &NVME_CTRL_CMIC_MULTI_CTRL ) && + info->is_shared)) { +dev_err (ctrl->device, +"ignoring nsid %d because of duplicate IDs\n" , + info->nsid); +return ret; + } + + dev_err(ctrl->device,
drivers/nvme/host/core.c static int nvme_init_ns_head(struct nvme_ns *ns, struct nvme_ns_info *info) · line 3470
Quoted 10 lines
drivers/nvme/host/core.c +7
-0+ "clearing duplicate IDs for nsid %d\n", info->nsid); +dev_err (ctrl->device, +"use of /dev/disk/by-id/ may cause data corruption\n" ); +memset (&info->ids.nguid,0 ,sizeof (info->ids.nguid)); +memset (&info->ids.uuid,0 ,sizeof (info->ids.uuid)); +memset (&info->ids.eui64,0 ,sizeof (info->ids.eui64)); + ctrl->quirks |=NVME_QUIRK_BOGUS_NID ; }mutex_lock (&ctrl->subsys->lock);
Hi,
I’d like to discuss whether we should revisit the duplicate-ID check for NVMe-oF transports, especially in HA dual-active setups.
In such HA configurations, a single LUN is exposed via multiple subsystems (one per storage controller) to provide redundancy. Because it represents the same namespace, it usually reports the same UUID/NGUID/EUI64 on all paths.
With the logic introduced in this patch, Fabrics are still strictly rejected:
drivers/nvme/host/core.c static int nvme_init_ns_head(struct nvme_ns *ns, struct nvme_ns_info *info) · line 3453
Quoted 3 lines
drivers/nvme/host/core.c +3
-0+if ((ns->ctrl->ops->flags &NVME_F_FABRICS ) ||/* !PCIe */ + ((ns->ctrl->subsys->cmic &NVME_CTRL_CMIC_MULTI_CTRL ) && + info->is_shared)) {
Concretely, with two subsystems exposing the same LUN in a dual-active HA configuration:
- Only paths from one subsystem are used;
- When that controller fails, the host cannot fail over to the other subsystem because its namespace was ignored, effectively breaking HA.
Would it make sense to:
1) relax the duplicate ID check for NVMe-oF HA dual-active use cases, or
2) add a module parameter (e.g., nvme_core.allow_duplicate_ids) so admins can opt-in when they know their storage topology and accept the /dev/disk/by-id risks?
Keeping the default strict is fine, but having an escape hatch would be very helpful for HA deployments.
Thanks,
Xiaoke
Christoph Hellwig
maintainerQuoted 8 lines · On Tue, Jan 20, 2026 at 05:54:25PM +0800, [email protected] wrote:
I’d like to discuss whether we should revisit the duplicate-ID check for NVMe-oF transports, especially in HA dual-active setups.
In such HA configurations, a single LUN is exposed via multiple subsystems (one per storage controller) to provide redundancy. Because it represents the same namespace, it usually reports the same UUID/NGUID/EUI64 on all paths.
Not in any configuration confirming to the NVMe spec (discounting the completely broken dispersed namespace feature).
So no, this is exactly what both the spec, and the code try to prevent.
Quoted 6 lines
drivers/nvme/host/core.c static int nvme_init_ns_head(struct nvme_ns *ns, struct nvme_ns_info *info) · line 3453
Quoted 3 lines
drivers/nvme/host/core.c +3
-0+if ((ns->ctrl->ops->flags &NVME_F_FABRICS ) ||/* !PCIe */ + ((ns->ctrl->subsys->cmic &NVME_CTRL_CMIC_MULTI_CTRL ) && + info->is_shared)) {Concretely, with two subsystems exposing the same LUN in a dual-active HA configuration:
There are no logical units or logical unit numbers in NVMe.