| commit | be8e3b0044a68e1f1002c432f6b40d290cf0701d | |
| author | Steve French <sfrench@us.ibm.com> | |
| Fri, 29 Apr 2011 05:40:20 +0000 (29 05:40 +0000) | ||
| committer | Steve French <sfrench@us.ibm.com> | |
| Thu, 19 May 2011 14:10:51 +0000 (19 14:10 +0000) | ||
| tree | 41f6a5e2ccf4bf03eb722030563490bbe46f0644 | treesnapshot (tar.gz zip) |
| parent | 9409ae58e0759d010b347e7b19ebc90ab5d4b98f | commitdiff |
consistently use smb_buf_length as be32 for cifs (try 3)
There is one big endian field in the cifs protocol, the RFC1001
length, which cifs code (unlike in the smb2 code) had been handling as
u32 until the last possible moment, when it was converted to be32 (its
native form) before sending on the wire. To remove the last sparse
endian warning, and to make this consistent with the smb2
implementation (which always treats the fields in their
native size and endianness), convert all uses of smb_buf_length to
be32.
This version incorporates Christoph's comment about
using be32_add_cpu, and fixes a typo in the second
version of the patch.
Signed-off-by: Steve French <sfrench@us.ibm.com>
Signed-off-by: Pavel Shilovsky <piastry@etersoft.ru>
Signed-off-by: Steve French <sfrench@us.ibm.com>
There is one big endian field in the cifs protocol, the RFC1001
length, which cifs code (unlike in the smb2 code) had been handling as
u32 until the last possible moment, when it was converted to be32 (its
native form) before sending on the wire. To remove the last sparse
endian warning, and to make this consistent with the smb2
implementation (which always treats the fields in their
native size and endianness), convert all uses of smb_buf_length to
be32.
This version incorporates Christoph's comment about
using be32_add_cpu, and fixes a typo in the second
version of the patch.
Signed-off-by: Steve French <sfrench@us.ibm.com>
Signed-off-by: Pavel Shilovsky <piastry@etersoft.ru>
Signed-off-by: Steve French <sfrench@us.ibm.com>