From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH] nvmet: better data length validation
Date: Thu, 9 Nov 2017 17:43:28 +0100 [thread overview]
Message-ID: <20171109164328.GA14453@lst.de> (raw)
In-Reply-To: <5effa992-70a1-72f5-4cca-86fae9cb6bd5@grimberg.me>
On Thu, Nov 09, 2017@06:41:24PM +0200, Sagi Grimberg wrote:
>
>> Currently the NVMe target stores the expexted data length in req->data_len
>> and uses that for data transfer decisions, but that does not take the
>> actual transfer length in the SGLs into account. So this adds a new
>> transfer_len field, into which the transport drivers store the actual
>> transfer length. We then check the two match before actually executing
>> the command.
>>
>> The FC transport driver already had such a field, which is removed in
>> favour of the common one.
>
> That will also be useful when we will have DIF support ;)
.. and for the passthrough driver as well.
next prev parent reply other threads:[~2017-11-09 16:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-09 13:29 [PATCH] nvmet: better data length validation Christoph Hellwig
2017-11-09 16:41 ` Sagi Grimberg
2017-11-09 16:43 ` Christoph Hellwig [this message]
2017-11-16 0:13 ` James Smart
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=20171109164328.GA14453@lst.de \
--to=hch@lst.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.