nvmet-tcp: fix maxh2cdata icresp parameter
authorSagi Grimberg <sagi@grimberg.me>
Wed, 26 Feb 2020 00:42:27 +0000 (16:42 -0800)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Fri, 17 Apr 2020 08:50:09 +0000 (10:50 +0200)
commit0eb4d8b985be17ce39038367f222081a3aae238a
tree9f8e5e83d77eb5c0b6bcc28def47ac90cbb6b9df
parentb3c7227ad4c686023e42bc52222540b552bf3141
nvmet-tcp: fix maxh2cdata icresp parameter

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