cifs: allow unlock flock and OFD lock across fork
authorMurphy Zhou <jencce.kernel@gmail.com>
Fri, 21 Feb 2020 02:30:01 +0000 (10:30 +0800)
committerSteve French <stfrench@microsoft.com>
Mon, 23 Mar 2020 03:49:09 +0000 (22:49 -0500)
Since commit d0677992d2af ("cifs: add support for flock") added
support for flock, LTP/flock03[1] testcase started to fail.

This testcase is testing flock lock and unlock across fork.
The parent locks file and starts the child process, in which
it unlock the same fd and lock the same file with another fd
again. All the lock and unlock operation should succeed.

Now the child process does not actually unlock the file, so
the following lock fails. Fix this by allowing flock and OFD
lock go through the unlock routine, not skipping if the unlock
request comes from another process.

Patch has been tested by LTP/xfstests on samba and Windows
server, v3.11, with or without cache=none mount option.

[1] https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/syscalls/flock/flock03.c
Signed-off-by: Murphy Zhou <jencce.kernel@gmail.com>
Signed-off-by: Steve French <stfrench@microsoft.com>
Acked-by: Pavel Shilovsky <pshilov@microsoft.com>
fs/cifs/smb2file.c

index 0a19d6d8e1cc521d8a424687560ba51574c9139b..2fa3ba354cc96770d8c7160c318f0c1cfc6e912b 100644 (file)
@@ -152,7 +152,12 @@ smb2_unlock_range(struct cifsFileInfo *cfile, struct file_lock *flock,
                    (li->offset + li->length))
                        continue;
                if (current->tgid != li->pid)
-                       continue;
+                       /*
+                        * flock and OFD lock are associated with an open
+                        * file description, not the process.
+                        */
+                       if (!(flock->fl_flags & (FL_FLOCK | FL_OFDLCK)))
+                               continue;
                if (cinode->can_cache_brlcks) {
                        /*
                         * We can cache brlock requests - simply remove a lock