Re: [PATCH 3/3] nvme: allow integrity when PI is not in first bytes
[
Date Prev
][
Date Next
][
Thread Prev
][
Thread Next
][
Date Index
][
Thread Index
]
To
: Kanchan Joshi <joshi.k@xxxxxxxxxxx>, kbusch@xxxxxxxxxx, axboe@xxxxxxxxx, hch@xxxxxx, martin.petersen@xxxxxxxxxx
Subject
: Re: [PATCH 3/3] nvme: allow integrity when PI is not in first bytes
From
: Sagi Grimberg <sagi@xxxxxxxxxxx>
Date
: Wed, 31 Jan 2024 14:43:25 +0200
Cc
: linux-nvme@xxxxxxxxxxxxxxxxxxx, linux-block@xxxxxxxxxxxxxxx, gost.dev@xxxxxxxxxxx
In-reply-to
: <
20240130171206.4845-4-joshi.k@samsung.com
>
References
: <
20240130171206.4845-1-joshi.k@samsung.com
> <CGME20240130171929epcas5p24f6c25d123d3cd6463cbef1aaf795276@epcas5p2.samsung.com> <
20240130171206.4845-4-joshi.k@samsung.com
>
User-agent
: Mozilla Thunderbird
Reviewed-by: Sagi Grimberg <sagi@xxxxxxxxxxx>
References
:
[PATCH 0/3] Block integrity with flexibile-offset PI
From:
Kanchan Joshi
[PATCH 3/3] nvme: allow integrity when PI is not in first bytes
From:
Kanchan Joshi
Prev by Date:
Re: [PATCH 2/3] block: support PI at non-zero offset within metadata
Next by Date:
Re: [PATCH 1/1] block: print warning when invalid domain set to ioprio
Previous by thread:
Re: [PATCH 3/3] nvme: allow integrity when PI is not in first bytes
Next by thread:
Re: [PATCH 0/3] Block integrity with flexibile-offset PI
Index(es):
Date
Thread
[Index of Archives]
[Linux RAID]
[Linux SCSI]
[Linux ATA RAID]
[IDE]
[Linux Wireless]
[Linux Kernel]
[ATH6KL]
[Linux Bluetooth]
[Linux Netdev]
[Kernel Newbies]
[Security]
[Git]
[Netfilter]
[Bugtraq]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Device Mapper]