aboutsummaryrefslogtreecommitdiffstats
path: root/crypto
diff options
context:
space:
mode:
authorJeff Layton <jlayton@redhat.com>2012-02-07 06:31:05 -0500
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2012-02-20 12:46:18 -0800
commit23cfecf97911af4ef38afd61879f030af0410755 (patch)
treeeb14ec7d6b53781fdd4ac98347a0397961a5cd2a /crypto
parent77d04b76d64e24329bb63d3d8d52c942db61bcb6 (diff)
downloadkernel_samsung_smdk4412-23cfecf97911af4ef38afd61879f030af0410755.zip
kernel_samsung_smdk4412-23cfecf97911af4ef38afd61879f030af0410755.tar.gz
kernel_samsung_smdk4412-23cfecf97911af4ef38afd61879f030af0410755.tar.bz2
cifs: don't return error from standard_receive3 after marking response malformed
commit ff4fa4a25a33f92b5653bb43add0c63bea98d464 upstream. standard_receive3 will check the validity of the response from the server (via checkSMB). It'll pass the result of that check to handle_mid which will dequeue it and mark it with a status of MID_RESPONSE_MALFORMED if checkSMB returned an error. At that point, standard_receive3 will also return an error, which will make the demultiplex thread skip doing the callback for the mid. This is wrong -- if we were able to identify the request and the response is marked malformed, then we want the demultiplex thread to do the callback. Fix this by making standard_receive3 return 0 in this situation. Reported-and-Tested-by: Mark Moseley <moseleymark@gmail.com> Signed-off-by: Jeff Layton <jlayton@redhat.com> Signed-off-by: Steve French <smfrench@gmail.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'crypto')
0 files changed, 0 insertions, 0 deletions