Re: [PATCH v2 2/3] block: support PI at non-zero offset within metadata
From: Keith Busch <kbusch@kernel.org>
Date: 2024-09-26 16:55:56
Also in:
linux-nvme
Possibly related (same subject, not in this thread)
- 2024-10-02 · Re: [PATCH v2 2/3] block: support PI at non-zero offset within metadata · Keith Busch <kbusch@kernel.org>
- 2024-10-02 · Re: [PATCH v2 2/3] block: support PI at non-zero offset within metadata · "Martin K. Petersen" <martin.petersen@oracle.com>
- 2024-10-02 · Re: [PATCH v2 2/3] block: support PI at non-zero offset within metadata · Javier González <hidden>
- 2024-10-01 · Re: [PATCH v2 2/3] block: support PI at non-zero offset within metadata · Keith Busch <kbusch@kernel.org>
- 2024-10-01 · Re: [PATCH v2 2/3] block: support PI at non-zero offset within metadata · Javier González <hidden>
On Thu, Sep 26, 2024 at 10:08:09PM +0530, Kanchan Joshi wrote:
But there are kernel knobs too. Hope you are able to get to the same state (as nop profile) by clearing write_generate and read_verify: echo 0 > /sys/block/nvme0n1/integrity/read_verify
It's not the kernel's verify causing the failure; it's the end device. For nvme, it'll return status 0x282, End-to-end Guard Check Error, so the kernel doesn't have a chance to check the data. We'd need to turn off the command's NVME_RW_PRINFO_PRCHK_GUARD flag, but there's currently no knob to toggle that.