lkml.org 
[lkml]   [2020]   [Apr]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    From
    Subject[PATCH 5.6 096/254] nvmet-tcp: fix maxh2cdata icresp parameter
    Date
    From: Sagi Grimberg <sagi@grimberg.me>

    commit 9cda34e37489244a8c8628617e24b2dbc8a8edad upstream.

    MAXH2CDATA is not zero based. Also no reason to limit ourselves to
    1M transfers as we can do more easily. Make this an arbitrary limit
    of 16M.

    Reported-by: Wenhua Liu <liuw@vmware.com>
    Cc: stable@vger.kernel.org # v5.0+
    Signed-off-by: Sagi Grimberg <sagi@grimberg.me>
    Signed-off-by: Keith Busch <kbusch@kernel.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

    ---
    drivers/nvme/target/tcp.c | 2 +-
    1 file changed, 1 insertion(+), 1 deletion(-)

    --- a/drivers/nvme/target/tcp.c
    +++ b/drivers/nvme/target/tcp.c
    @@ -794,7 +794,7 @@ static int nvmet_tcp_handle_icreq(struct
    icresp->hdr.pdo = 0;
    icresp->hdr.plen = cpu_to_le32(icresp->hdr.hlen);
    icresp->pfv = cpu_to_le16(NVME_TCP_PFV_1_0);
    - icresp->maxdata = cpu_to_le32(0xffff); /* FIXME: support r2t */
    + icresp->maxdata = cpu_to_le32(0x400000); /* 16M arbitrary limit */
    icresp->cpda = 0;
    if (queue->hdr_digest)
    icresp->digest |= NVME_TCP_HDR_DIGEST_ENABLE;

    \
     
     \ /
      Last update: 2020-04-16 16:57    [W:2.070 / U:0.380 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site