Skip to content

Commit e2a9c43

Browse files
sprasad-microsoftjohn-cabaj
authored andcommitted
cifs: generate signkey for the channel that's reconnecting
BugLink: https://bugs.launchpad.net/bugs/2036450 Before my changes to how multichannel reconnects work, the primary channel was always used to do a non-binding session setup. With my changes, that is not the case anymore. Missed this place where channel at index 0 was forcibly updated with the signing key. Signed-off-by: Shyam Prasad N <sprasad@microsoft.com> Reviewed-by: Paulo Alcantara (SUSE) <pc@manguebit.com> Cc: stable@vger.kernel.org Signed-off-by: Steve French <stfrench@microsoft.com> (cherry picked from commit 05ce044) Signed-off-by: Tim Gardner <tim.gardner@canonical.com>
1 parent e3cc7f1 commit e2a9c43

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

fs/cifs/smb2transport.c

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -425,7 +425,7 @@ generate_smb3signingkey(struct cifs_ses *ses,
425425

426426
/* safe to access primary channel, since it will never go away */
427427
spin_lock(&ses->chan_lock);
428-
memcpy(ses->chans[0].signkey, ses->smb3signingkey,
428+
memcpy(ses->chans[chan_index].signkey, ses->smb3signingkey,
429429
SMB3_SIGN_KEY_SIZE);
430430
spin_unlock(&ses->chan_lock);
431431

0 commit comments

Comments
 (0)