From: Klaus Jensen <its@irrelevant.dk>
To: linux-nvme@lists.infradead.org
Cc: Keith Busch <kbusch@kernel.org>, Christoph Hellwig <hch@lst.de>,
Jens Axboe <axboe@fb.com>, Sagi Grimberg <sagi@grimberg.me>,
linux-kernel@vger.kernel.org, Klaus Jensen <k.jensen@samsung.com>
Subject: Re: [PATCH] nvme: fix write zeroes pi
Date: Wed, 10 Nov 2021 09:43:28 +0100 [thread overview]
Message-ID: <YYuGMBYaiZD2vybH@apples.localdomain> (raw)
In-Reply-To: <20211104181618.864157-1-its@irrelevant.dk>
[-- Attachment #1: Type: text/plain, Size: 1400 bytes --]
On Nov 4 19:16, Klaus Jensen wrote:
> From: Klaus Jensen <k.jensen@samsung.com>
>
> Write Zeroes sets PRACT when block integrity is enabled (as it should),
> but neglects to also set the reftag which is expected by reads. This
> causes protection errors on reads.
>
> Fix this by setting the reftag for type 1 and 2 (for type 3, reads will
> not check the reftag).
>
> Signed-off-by: Klaus Jensen <k.jensen@samsung.com>
> ---
> drivers/nvme/host/core.c | 11 ++++++++---
> 1 file changed, 8 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/nvme/host/core.c b/drivers/nvme/host/core.c
> index 3825b596ca16..532bad4de025 100644
> --- a/drivers/nvme/host/core.c
> +++ b/drivers/nvme/host/core.c
> @@ -914,10 +914,15 @@ static inline blk_status_t nvme_setup_write_zeroes(struct nvme_ns *ns,
> cpu_to_le64(nvme_sect_to_lba(ns, blk_rq_pos(req)));
> cmnd->write_zeroes.length =
> cpu_to_le16((blk_rq_bytes(req) >> ns->lba_shift) - 1);
> - if (nvme_ns_has_pi(ns))
> +
> + switch (ns->pi_type) {
> + case NVME_NS_DPS_PI_TYPE1:
> + case NVME_NS_DPS_PI_TYPE2:
> cmnd->write_zeroes.control = cpu_to_le16(NVME_RW_PRINFO_PRACT);
> - else
> - cmnd->write_zeroes.control = 0;
> + cmnd->write_zeroes.reftag = cpu_to_le32(t10_pi_ref_tag(req));
> + break;
> + }
> +
> return BLK_STS_OK;
> }
>
Ugh. I goofed up. This fails to set PRACT for type 3.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2021-11-10 8:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-04 18:16 [PATCH] nvme: fix write zeroes pi Klaus Jensen
2021-11-05 3:23 ` Martin K. Petersen
2021-11-10 6:10 ` Chaitanya Kulkarni
2021-11-10 9:16 ` Klaus Jensen
2021-11-11 5:06 ` Chaitanya Kulkarni
2021-11-10 8:43 ` Klaus Jensen [this message]
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=YYuGMBYaiZD2vybH@apples.localdomain \
--to=its@irrelevant.dk \
--cc=axboe@fb.com \
--cc=hch@lst.de \
--cc=k.jensen@samsung.com \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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