diff options
| author | Varun Prakash <[email protected]> | 2022-01-22 16:57:44 +0000 |
|---|---|---|
| committer | Christoph Hellwig <[email protected]> | 2022-02-23 13:43:11 +0000 |
| commit | c2700d2886a87f83f31e0a301de1d2350b52c79b (patch) | |
| tree | dbcfa128fca5672102867f2ea87cd56134164865 /drivers/net/xen-netfront.c | |
| parent | nvme: also mark passthrough-only namespaces ready in nvme_update_ns_info (diff) | |
| download | kernel-c2700d2886a87f83f31e0a301de1d2350b52c79b.tar.gz kernel-c2700d2886a87f83f31e0a301de1d2350b52c79b.zip | |
nvme-tcp: send H2CData PDUs based on MAXH2CDATA
As per NVMe/TCP specification (revision 1.0a, section 3.6.2.3)
Maximum Host to Controller Data length (MAXH2CDATA): Specifies the
maximum number of PDU-Data bytes per H2CData PDU in bytes. This value
is a multiple of dwords and should be no less than 4,096.
Current code sets H2CData PDU data_length to r2t_length,
it does not check MAXH2CDATA value. Fix this by setting H2CData PDU
data_length to min(req->h2cdata_left, queue->maxh2cdata).
Also validate MAXH2CDATA value returned by target in ICResp PDU,
if it is not a multiple of dword or if it is less than 4096 return
-EINVAL from nvme_tcp_init_connection().
Signed-off-by: Varun Prakash <[email protected]>
Reviewed-by: Sagi Grimberg <[email protected]>
Signed-off-by: Christoph Hellwig <[email protected]>
Diffstat (limited to 'drivers/net/xen-netfront.c')
0 files changed, 0 insertions, 0 deletions