Commit 8d33096a authored Jul 25, 2019 by Steve French

smb3: send CAP_DFS capability during session setup



We had a report of a server which did not do a DFS referral
because the session setup Capabilities field was set to 0
(unlike negotiate protocol where we set CAP_DFS).  Better to
send it session setup in the capabilities as well (this also
more closely matches Windows client behavior).

Signed-off-by: Steve French <stfrench@microsoft.com>
Reviewed-off-by: Ronnie Sahlberg <lsahlber@redhat.com>
Reviewed-by: Pavel Shilovsky <pshilov@microsoft.com>
CC: Stable <stable@vger.kernel.org>

parent 3edeb4a4

fs/cifs/smb2pdu.c

+5 −0

Original line number	Original line	Diff line number	Diff line
	@@ -1196,7 +1196,12 @@ SMB2_sess_alloc_buffer(struct SMB2_sess_data *sess_data)
	else		else
	req->SecurityMode = 0;		req->SecurityMode = 0;

			#ifdef CONFIG_CIFS_DFS_UPCALL
			req->Capabilities = cpu_to_le32(SMB2_GLOBAL_CAP_DFS);
			#else
	req->Capabilities = 0;		req->Capabilities = 0;
			#endif /* DFS_UPCALL */

	req->Channel = 0; /* MBZ */		req->Channel = 0; /* MBZ */

	sess_data->iov[0].iov_base = (char *)req;		sess_data->iov[0].iov_base = (char *)req;