[PATCH for-next v5 3/4] nvme: set pi_offset only when checksum type is not BLK_INTEGRITY_CSUM_NONE
Anuj Gupta
anuj20.g at samsung.com
Mon Jun 30 02:05:47 PDT 2025
protection information is treated as opaque when checksum type is
BLK_INTEGRITY_CSUM_NONE. In order to maintain the right metadata
semantics, set pi_offset only in cases where checksum type is not
BLK_INTEGRITY_CSUM_NONE.
Signed-off-by: Anuj Gupta <anuj20.g at samsung.com>
Reviewed-by: Christoph Hellwig <hch at lst.de>
Reviewed-by: Martin K. Petersen <martin.petersen at oracle.com>
---
drivers/nvme/host/core.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/nvme/host/core.c b/drivers/nvme/host/core.c
index 685dea0f23a3..500a9e82d60e 100644
--- a/drivers/nvme/host/core.c
+++ b/drivers/nvme/host/core.c
@@ -1867,9 +1867,10 @@ static bool nvme_init_integrity(struct nvme_ns_head *head,
}
bi->metadata_size = head->ms;
- if (bi->csum_type)
+ if (bi->csum_type) {
bi->pi_tuple_size = head->pi_size;
- bi->pi_offset = info->pi_offset;
+ bi->pi_offset = info->pi_offset;
+ }
return true;
}
--
2.25.1
More information about the Linux-nvme
mailing list