diff options
author | Jeff Layton <jlayton@redhat.com> | 2011-10-19 15:29:59 -0400 |
---|---|---|
committer | Jeff Layton <jlayton@redhat.com> | 2011-10-19 15:29:59 -0400 |
commit | 2ab2593f4b8953ff951f5531e695e487dfe0b51f (patch) | |
tree | ad5be299146015bea9f83c066ebf11a2b26454ff /fs/cifs | |
parent | 44d22d846fdc7c3e688fc1ff5ae6d06d08bb5656 (diff) | |
download | linux-2ab2593f4b8953ff951f5531e695e487dfe0b51f.tar.bz2 |
cifs: fix protocol definition for READ_RSP
There is no pad, and it simplifies the code to remove the "Data" field.
None of the existing code relies on these fields, or on the READ_RSP
being a particular length.
Reviewed-and-Tested-by: Pavel Shilovsky <piastry@etersoft.ru>
Signed-off-by: Jeff Layton <jlayton@redhat.com>
Diffstat (limited to 'fs/cifs')
-rw-r--r-- | fs/cifs/cifspdu.h | 4 |
1 files changed, 1 insertions, 3 deletions
diff --git a/fs/cifs/cifspdu.h b/fs/cifs/cifspdu.h index de3aa285de03..3c6ef34fe2bc 100644 --- a/fs/cifs/cifspdu.h +++ b/fs/cifs/cifspdu.h @@ -1089,9 +1089,7 @@ typedef struct smb_com_read_rsp { __le16 DataLengthHigh; __u64 Reserved2; __u16 ByteCount; - __u8 Pad; /* BB check for whether padded to DWORD - boundary and optimum performance here */ - char Data[1]; + /* read response data immediately follows */ } __attribute__((packed)) READ_RSP; typedef struct locking_andx_range { |