From: Jeff Layton <jlayton@redhat.com>
Date: Wed, 16 Mar 2011 19:15:30 +0000 (-0400)
Subject: cifs: fix broken BCC check in is_valid_oplock_break
X-Git-Url: https://git.stricted.de/?a=commitdiff_plain;h=8679b0dba7cb98842cbe37f61ef05ef64106334c;p=GitHub%2FLineageOS%2Fandroid_kernel_motorola_exynos9610.git

cifs: fix broken BCC check in is_valid_oplock_break

The BCC is still __le16 at this point, and in any case we need to
use the get_bcc_le macro to make sure we don't hit alignment
problems.

Signed-off-by: Jeff Layton <jlayton@redhat.com>
Signed-off-by: Steve French <sfrench@us.ibm.com>
---

diff --git a/fs/cifs/misc.c b/fs/cifs/misc.c
index 7228179ef5b0..0c684ae4c071 100644
--- a/fs/cifs/misc.c
+++ b/fs/cifs/misc.c
@@ -521,7 +521,7 @@ is_valid_oplock_break(struct smb_hdr *buf, struct TCP_Server_Info *srv)
 			(struct smb_com_transaction_change_notify_rsp *)buf;
 		struct file_notify_information *pnotify;
 		__u32 data_offset = 0;
-		if (pSMBr->ByteCount > sizeof(struct file_notify_information)) {
+		if (get_bcc_le(buf) > sizeof(struct file_notify_information)) {
 			data_offset = le32_to_cpu(pSMBr->DataOffset);
 
 			pnotify = (struct file_notify_information *)