[PATCH 0/6] block: add support for REQ_OP_VERIFY
Keith Busch
kbusch at kernel.org
Sun Dec 4 12:29:44 PST 2022
On Sat, Dec 03, 2022 at 07:19:17AM +0300, Javier González wrote:
>
> > On 2 Dec 2022, at 17.58, Keith Busch <kbusch at kernel.org> wrote:
> >
> > On Fri, Dec 02, 2022 at 08:16:30AM +0100, Hannes Reinecke wrote:
> >>> On 12/1/22 20:39, Matthew Wilcox wrote:
> >>> On Thu, Dec 01, 2022 at 06:12:46PM +0000, Chaitanya Kulkarni wrote:
> >>>> So nobody can get away with a lie.
> >>>
> >>> And yet devices do exist which lie. I'm not surprised that vendors
> >>> vehemently claim that they don't, or "nobody would get away with it".
> >>> But, of course, they do. And there's no way for us to find out if
> >>> they're lying!
> >>>
> >> But we'll never be able to figure that out unless we try.
> >>
> >> Once we've tried we will have proof either way.
> >
> > As long as the protocols don't provide proof-of-work, trying this
> > doesn't really prove anything with respect to this concern.
>
> Is this something we should bring to NVMe? Seems like the main disagreement can be addressed there.
Yeah, proof for the host appears to require a new feature, so we'd need
to bring this to the TWG. I can draft a TPAR if there's interest and
have ideas on how the feature could be implemented, but I currently
don't have enough skin in this game to sponser it.
More information about the Linux-nvme
mailing list