diff options
| author |   Tao Jiang <tanroame.kyle@gmail.com> | 2026-04-16 01:27:15 +0800 |
|---|---|---|
| committer |   Keith Busch <kbusch@kernel.org> | 2026-04-16 15:11:14 -0700 |
| commit | cf92d78a4aa2adbc2b1e687776aabe63c5b97f3f (patch) | |
| tree | 2350f6ead0ed0340160166121ad124a8d13d8f21 /tools/testing/selftests/dm-verity/git:/ssh:/git@git.zx2c4.com | |
| parent | nvme-multipath: put module reference when delayed removal work is canceled (diff) | |
nvme-pci: add quirk for Memblaze Pblaze5 (0x1c5f:0x0555)
The Memblaze Pblaze5 NVMe device (PCI ID 0x1c5f:0x0555)
is detected as a controller on recent kernels (tested on 5.15.85
and 6.8.4), but no namespace is exposed.
Tools like lsblk and fdisk do not report any block device.
dmesg shows:
nvme nvme0: missing or invalid SUBNQN field.
The device works correctly on older kernels (e.g. 4.19), suggesting
a compatibility issue with newer namespace handling.
This indicates the device does not properly support the
Namespace Descriptor List feature.
Applying NVME_QUIRK_NO_NS_DESC_LIST allows the namespace to be
discovered correctly.
Reviewed-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
Signed-off-by: Tao Jiang <tanroame.kyle@gmail.com>
Signed-off-by: Keith Busch <kbusch@kernel.org>
Diffstat (limited to 'tools/testing/selftests/dm-verity/git:/ssh:/git@git.zx2c4.com')
0 files changed, 0 insertions, 0 deletions