cifs: adjust sequence number downward after signing NT_CANCEL request
authorJeff Layton <jlayton@redhat.com>
Thu, 27 Dec 2012 13:05:03 +0000 (08:05 -0500)
committerBen Hutchings <ben@decadent.org.uk>
Wed, 16 Jan 2013 01:13:13 +0000 (01:13 +0000)
commitf6f82cba2ccbf6a77278c7c3f2e4daf23063944a
treee613ce5621e5175c62a6377d918eaf68a3dc7949
parentc41fba2f3cb4ebc9be9fc91fe339965c234d940f
cifs: adjust sequence number downward after signing NT_CANCEL request

commit 31efee60f489c759c341454d755a9fd13de8c03d upstream.

When a call goes out, the signing code adjusts the sequence number
upward by two to account for the request and the response. An NT_CANCEL
however doesn't get a response of its own, it just hurries the server
along to get it to respond to the original request more quickly.
Therefore, we must adjust the sequence number back down by one after
signing a NT_CANCEL request.

Reported-by: Tim Perry <tdparmor-sambabugs@yahoo.com>
Signed-off-by: Jeff Layton <jlayton@redhat.com>
Signed-off-by: Steve French <smfrench@gmail.com>
[bwh: Backported to 3.2: adjust filename]
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
fs/cifs/transport.c