From: Christoph Hellwig <hch@lst.de>
To: M Nikhil <nikh1092@linux.ibm.com>
Cc: linux-block@vger.kernel.org, dm-devel@lists.linux.dev,
linux-raid@vger.kernel.org, nvdimm@lists.linux.dev,
linux-scsi@vger.kernel.org, hare@suse.de, hch@lst.de,
steffen Maier <maier@linux.ibm.com>,
Benjamin Block <bblock@linux.ibm.com>,
Nihar Panda <niharp@linux.ibm.com>
Subject: Re: Change in reported values of some block integrity sysfs attributes
Date: Fri, 13 Dec 2024 15:33:51 +0100 [thread overview]
Message-ID: <20241213143351.GB16111@lst.de> (raw)
In-Reply-To: <f6130475-3ccd-45d2-abde-3ccceada0f0a@linux.ibm.com>
Hi M,
On Fri, Dec 13, 2024 at 12:46:14PM +0530, M Nikhil wrote:
> Hi Everyone,
>
> * We have observed change in the values of some of the block integrity
> sysfs attributes for the block devices on the master branch. The
> sysfs attributes related to block device integrity , write_generate
> and read_verify are enabled for the block device when the parameter
> device_is_integrity_capable is disabled. This behaviour is seen on
> the scsi disks irrespective of DIF protection enabled or disabled on
> the disks.
As in after a "echo 1 > /sys/.../device_is_integrity_capable" ?
I'll look into it.
next prev parent reply other threads:[~2024-12-13 14:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 7:16 Change in reported values of some block integrity sysfs attributes M Nikhil
2024-12-13 14:33 ` Christoph Hellwig [this message]
2024-12-17 12:46 ` M Nikhil
2024-12-13 22:30 ` Martin K. Petersen
2024-12-17 12:39 ` M Nikhil
2025-02-21 6:01 ` M Nikhil
2025-02-21 10:37 ` Anuj gupta
2025-02-21 10:35 ` Anuj Gupta
2025-02-21 12:07 ` Anuj Gupta
2025-02-25 1:07 ` Martin K. Petersen
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=20241213143351.GB16111@lst.de \
--to=hch@lst.de \
--cc=bblock@linux.ibm.com \
--cc=dm-devel@lists.linux.dev \
--cc=hare@suse.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=maier@linux.ibm.com \
--cc=niharp@linux.ibm.com \
--cc=nikh1092@linux.ibm.com \
--cc=nvdimm@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).