From: Anuj Gupta <anuj20.g@samsung.com>
To: axboe@kernel.dk, hch@lst.de, kbusch@kernel.org,
martin.petersen@oracle.com
Cc: anuj1072538@gmail.com, nikh1092@linux.ibm.com,
linux-nvme@lists.infradead.org, linux-block@vger.kernel.org,
linux-scsi@vger.kernel.org, dm-devel@lists.linux.dev,
Anuj Gupta <anuj20.g@samsung.com>
Subject: [PATCH v1 0/3] Fix integrity sysfs reporting inconsistencies across NVMe, SCSI, and DM
Date: Tue, 25 Feb 2025 10:16:50 +0530 [thread overview]
Message-ID: <20250225044653.6867-1-anuj20.g@samsung.com> (raw)
In-Reply-To: CGME20250225045511epcas5p2d89efcac39b6553317e93e8c7fea3f2b@epcas5p2.samsung.com
This patch series addresses inconsistencies in block integrity sysfs
reporting across NVMe, SCSI, and device-mapper (DM) stacked devices.
Patch 1: Ensures DM devices correctly propagate device_is_integrity_capable
and properly report read_verify and write_generate sysfs attributes
Patch 2: Fixes NVMe integrity sysfs attributes for namespaces without
PI support.
Patch 3: Corrects SCSI integrity reporting when the HBA does not support
DIX.
Anuj Gupta (3):
block: Fix incorrect integrity sysfs reporting for DM devices
nvme: Fix incorrect block integrity sysfs values for non-PI namespaces
scsi: Fix incorrect integrity sysfs values when HBA doesn't support
DIX
block/blk-settings.c | 9 +++++++--
drivers/nvme/host/core.c | 4 ++++
drivers/scsi/sd_dif.c | 4 +++-
3 files changed, 14 insertions(+), 3 deletions(-)
--
2.25.1
next parent reply other threads:[~2025-02-25 5:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250225045511epcas5p2d89efcac39b6553317e93e8c7fea3f2b@epcas5p2.samsung.com>
2025-02-25 4:46 ` Anuj Gupta [this message]
2025-02-25 4:46 ` [PATCH v1 1/3] block: Fix incorrect integrity sysfs reporting for DM devices Anuj Gupta
2025-02-25 15:06 ` Christoph Hellwig
2025-02-26 11:27 ` Anuj gupta
2025-02-25 4:46 ` [PATCH v1 2/3] nvme: Fix incorrect block integrity sysfs values for non-PI namespaces Anuj Gupta
2025-02-25 15:07 ` Christoph Hellwig
2025-02-25 4:46 ` [PATCH v1 3/3] scsi: Fix incorrect integrity sysfs values when HBA doesn't support DIX Anuj Gupta
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=20250225044653.6867-1-anuj20.g@samsung.com \
--to=anuj20.g@samsung.com \
--cc=anuj1072538@gmail.com \
--cc=axboe@kernel.dk \
--cc=dm-devel@lists.linux.dev \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=nikh1092@linux.ibm.com \
/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