]> git.proxmox.com Git - mirror_ubuntu-artful-kernel.git/commit
cifs: release auth_key.response for reconnect.
authorShu Wang <shuwang@redhat.com>
Fri, 8 Sep 2017 10:48:33 +0000 (18:48 +0800)
committerSeth Forshee <seth.forshee@canonical.com>
Thu, 12 Oct 2017 21:19:58 +0000 (16:19 -0500)
commit39f7248d67988bcd233b47596961f04582fd6c24
treedf4c142d6f15caf2639d84b213652d046333ca59
parent4c59e6307b52d79ff44bfa2ac892ad829e3165a8
cifs: release auth_key.response for reconnect.

BugLink: http://bugs.launchpad.net/bugs/1721777
commit f5c4ba816315d3b813af16f5571f86c8d4e897bd upstream.

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>
Reviewed-by: Ronnie Sahlberg <lsahlber@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
fs/cifs/connect.c