diff options
author | Shu Wang <shuwang@redhat.com> | 2017-09-08 18:48:33 +0800 |
---|---|---|
committer | Steve French <smfrench@gmail.com> | 2017-09-20 18:46:23 -0500 |
commit | f5c4ba816315d3b813af16f5571f86c8d4e897bd (patch) | |
tree | f9affec59b8748da95e0bff0213ed5842961d659 /fs/cifs/smb2pdu.c | |
parent | 94183331e815617246b1baa97e0916f358c794bb (diff) | |
download | linux-f5c4ba816315d3b813af16f5571f86c8d4e897bd.tar.bz2 |
cifs: release auth_key.response for reconnect.
There is a race that cause cifs reconnect in cifs_mount,
- cifs_mount
- cifs_get_tcp_session
- [ start thread cifs_demultiplex_thread
- cifs_read_from_socket: -ECONNABORTED
- DELAY_WORK smb2_reconnect_server ]
- cifs_setup_session
- [ smb2_reconnect_server ]
auth_key.response was allocated in cifs_setup_session, and
will release when the session destoried. So when session re-
connect, auth_key.response should be check and released.
Tested with my system:
CIFS VFS: Free previous auth_key.response = ffff8800320bbf80
A simple auth_key.response allocation call trace:
- cifs_setup_session
- SMB2_sess_setup
- SMB2_sess_auth_rawntlmssp_authenticate
- build_ntlmssp_auth_blob
- setup_ntlmv2_rsp
Signed-off-by: Shu Wang <shuwang@redhat.com>
Signed-off-by: Steve French <smfrench@gmail.com>
CC: Stable <stable@vger.kernel.org>
Reviewed-by: Ronnie Sahlberg <lsahlber@redhat.com>
Diffstat (limited to 'fs/cifs/smb2pdu.c')
0 files changed, 0 insertions, 0 deletions