Skip to content

Commit 6e5e64c

Browse files
sprasad-microsoftsmfrench
authored andcommitted
cifs: do not reset chan_max if multichannel is not supported at mount
If the mount command has specified multichannel as a mount option, but multichannel is found to be unsupported by the server at the time of mount, we set chan_max to 1. Which means that the user needs to remount the share if the server starts supporting multichannel. This change removes this reset. What it means is that if the user specified multichannel or max_channels during mount, and at this time, multichannel is not supported, but the server starts supporting it at a later point, the client will be capable of scaling out the number of channels. Cc: [email protected] Signed-off-by: Shyam Prasad N <[email protected]> Signed-off-by: Steve French <[email protected]>
1 parent c3326a6 commit 6e5e64c

File tree

1 file changed

+0
-1
lines changed

1 file changed

+0
-1
lines changed

fs/smb/client/sess.c

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -186,7 +186,6 @@ int cifs_try_adding_channels(struct cifs_sb_info *cifs_sb, struct cifs_ses *ses)
186186
}
187187

188188
if (!(server->capabilities & SMB2_GLOBAL_CAP_MULTI_CHANNEL)) {
189-
ses->chan_max = 1;
190189
spin_unlock(&ses->chan_lock);
191190
cifs_server_dbg(VFS, "no multichannel support\n");
192191
return 0;

0 commit comments

Comments
 (0)