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>
This commit is contained in:
parent
44d22d846f
commit
2ab2593f4b
|
@ -1089,9 +1089,7 @@ typedef struct smb_com_read_rsp {
|
||||||
__le16 DataLengthHigh;
|
__le16 DataLengthHigh;
|
||||||
__u64 Reserved2;
|
__u64 Reserved2;
|
||||||
__u16 ByteCount;
|
__u16 ByteCount;
|
||||||
__u8 Pad; /* BB check for whether padded to DWORD
|
/* read response data immediately follows */
|
||||||
boundary and optimum performance here */
|
|
||||||
char Data[1];
|
|
||||||
} __attribute__((packed)) READ_RSP;
|
} __attribute__((packed)) READ_RSP;
|
||||||
|
|
||||||
typedef struct locking_andx_range {
|
typedef struct locking_andx_range {
|
||||||
|
|
Loading…
Reference in New Issue