nvme-pci: add BOGUS_NID quirk for Samsung PM1733

JIRA: https://issues.redhat.com/browse/RHEL-89350
Upstream Status: RHEL-only

Customers in the field are encountering issues with some firmware
versions of the Samsung PM1733 NVMe solid state drive, where a non-zero
value is present in the EUI64 identifier of a namespace, but is only
unique to the controller.  The NGUID value is non-zero, and unique
identifiers for namespaces created by this drive are unique; only the
common EUI64 between multiple namespaces create a problem.  This is not
an issue if there is only one namespace attached to the device, but
upstream commit e2724cb added a stricter check for identifiers,
which results in the inability to attach namespaces beyond the first
attached namespace.

Signed-off-by: Bryan Gurney <bgurney@redhat.com>

Author: bgurney-rh

drivers/nvme/host/pci.c

@@ -3466,6 +3466,8 @@ static const struct pci_device_id nvme_id_table[] = {
 		.driver_data = NVME_QUIRK_DELAY_BEFORE_CHK_RDY |
 				NVME_QUIRK_DISABLE_WRITE_ZEROES|
 				NVME_QUIRK_IGNORE_DEV_SUBNQN, },
+	{ PCI_DEVICE(0x144d, 0xa824),   /* Samsung PM1733 */
+		.driver_data = NVME_QUIRK_BOGUS_NID, },
 	{ PCI_DEVICE(0x15b7, 0x5008),   /* Sandisk SN530 */
 		.driver_data = NVME_QUIRK_BROKEN_MSI },
 	{ PCI_DEVICE(0x1987, 0x5012),	/* Phison E12 */