SMB client in Azure having handle leak issue

Issue

• We noticed that there is a Handle leak issue observed in RHEL cifs client and there are two scenarios:
  1) When file metadata is cached on the client but the file was renamed into another existing file on the server by another client. The client accessing the file gets FileID from the server which doesn't match the cached one. Then the client fails open system call with an handle being opened on the cloud side. Other rare cases (e.g. low memory) might cause a similar behavior.
  2) When a process waiting for a SMB2_CREATE response inside the kernel was interrupted by the signal (ex: The application was killed). In that case the client doesn’t recognize a response when it finally came thus leaking an open handle on the cloud side.
• The error below is shown in /var/log/messages on CIFS Client during the issue time:

May 22 22:46:40 CIFS-Client kernel: CIFS VFS: Close unmatched open
May 22 23:18:13 CIFS-Client kernel: CIFS VFS: Close unmatched open
......
May 22 23:27:45 CIFS-Client kernel: CIFS VFS: Close unmatched open
May 25 22:14:26 CIFS-Client kernel: CIFS VFS: Close unmatched open