Charge at least one credit, if server says that it supports multicredit
authorSteve French <smfrench@gmail.com>
Sun, 23 Jun 2013 23:43:37 +0000 (18:43 -0500)
committerSteve French <smfrench@gmail.com>
Wed, 26 Jun 2013 22:26:03 +0000 (17:26 -0500)
commit2b80d049eb6dd08431f63fc0c5ce78567648a033
tree2102c089ab4d97e0b8b98691f384c836d1d5d9b1
parent7f6538585eccdd7e663df3c6186486ef528d9c90
Charge at least one credit, if server says that it supports multicredit

In SMB2.1 and later the server will usually set the large MTU flag, and
we need to charge at least one credit, if server says that since
it supports multicredit.  Windows seems to let us get away with putting
a zero there, but they confirmed that it is wrong and the spec says
to put one there (if the request is under 64K and the CAP_LARGE_MTU
was returned during protocol negotiation by the server.

CC: Pavel Shilovsky <piastry@etersoft.ru>
Signed-off-by: Steve French <smfrench@gmail.com>
fs/cifs/smb2pdu.c