linux-stable.git/fs/locks.c, branch v4.4.2

locks: cleanup posix_lock_inode_wait and flock_lock_inode_wait

2015-10-22T18:57:42+00:00

All callers use locks_lock_inode_wait() instead.

Signed-off-by: Benjamin Coddington 
Signed-off-by: Jeff Layton

Move locks API users to locks_lock_inode_wait()

2015-10-22T18:57:36+00:00

Instead of having users check for FL_POSIX or FL_FLOCK to call the correct
locks API function, use the check within locks_lock_inode_wait().  This
allows for some later cleanup.

Signed-off-by: Benjamin Coddington 
Signed-off-by: Jeff Layton

locks: introduce locks_lock_inode_wait()

2015-10-22T18:57:20+00:00

Users of the locks API commonly call either posix_lock_file_wait() or
flock_lock_file_wait() depending upon the lock type.  Add a new function
locks_lock_inode_wait() which will check and call the correct function for
the type of lock passed in.

Signed-off-by: Benjamin Coddington 
Signed-off-by: Jeff Layton

locks: Use more file_inode and fix a comment

2015-10-15T13:07:07+00:00

Signed-off-by: Benjamin Coddington 
Signed-off-by: Jeff Layton

fs: fix data races on inode->i_flctx

2015-09-21T11:27:35+00:00

locks_get_lock_context() uses cmpxchg() to install i_flctx.
cmpxchg() is a release operation which is correct. But it uses
a plain load to load i_flctx. This is incorrect. Subsequent loads
from i_flctx can hoist above the load of i_flctx pointer itself
and observe uninitialized garbage there. This in turn can lead
to corruption of ctx->flc_lock and other members.

Documentation/memory-barriers.txt explicitly requires to use
a barrier in such context:
"A load-load control dependency requires a full read memory barrier".

Use smp_load_acquire() in locks_get_lock_context() and in bunch
of other functions that can proceed concurrently with
locks_get_lock_context().

The data race was found with KernelThreadSanitizer (KTSAN).

Signed-off-by: Dmitry Vyukov 
Signed-off-by: Jeff Layton

fs: fix fs/locks.c kernel-doc warning

2015-08-31T20:27:25+00:00

Fix kernel-doc warnings in fs/locks.c:

Warning(..//fs/locks.c:1577): No description found for parameter 'flags'

Signed-off-by: Randy Dunlap 
Signed-off-by: Jeff Layton

locks: inline posix_lock_file_wait and flock_lock_file_wait

2015-07-13T10:29:11+00:00

They just call file_inode and then the corresponding *_inode_file_wait
function. Just make them static inlines instead.

Signed-off-by: Jeff Layton

locks: new helpers - flock_lock_inode_wait and posix_lock_inode_wait

2015-07-13T10:29:11+00:00

Allow callers to pass in an inode instead of a filp.

Signed-off-by: Jeff Layton 
Reviewed-by: "J. Bruce Fields" 
Tested-by: "J. Bruce Fields"

locks: have flock_lock_file take an inode pointer instead of a filp

2015-07-13T10:29:11+00:00

...and rename it to better describe how it works.

In order to fix a use-after-free in NFS, we need to be able to remove
locks from an inode after the filp associated with them may have already
been freed. flock_lock_file already only dereferences the filp to get to
the inode, so just change it so the callers do that.

All of the callers already pass in a lock request that has the fl_file
set properly, so we don't need to pass it in individually. With that
change it now only dereferences the filp to get to the inode, so just
push that out to the callers.

Signed-off-by: Jeff Layton 
Reviewed-by: "J. Bruce Fields" 
Tested-by: "J. Bruce Fields"

proc: show locks in /proc/pid/fdinfo/X

2015-04-17T13:04:12+00:00

Let's show locks which are associated with a file descriptor in
its fdinfo file.

Currently we don't have a reliable way to determine who holds a lock.  We
can find some information in /proc/locks, but PID which is reported there
can be wrong.  For example, a process takes a lock, then forks a child and
dies.  In this case /proc/locks contains the parent pid, which can be
reused by another process.

$ cat /proc/locks
...
6: FLOCK  ADVISORY  WRITE 324 00:13:13431 0 EOF
...

$ ps -C rpcbind
  PID TTY          TIME CMD
  332 ?        00:00:00 rpcbind

$ cat /proc/332/fdinfo/4
pos:	0
flags:	0100000
mnt_id:	22
lock:	1: FLOCK  ADVISORY  WRITE 324 00:13:13431 0 EOF

$ ls -l /proc/332/fd/4
lr-x------ 1 root root 64 Mar  5 14:43 /proc/332/fd/4 -> /run/rpcbind.lock

$ ls -l /proc/324/fd/
total 0
lrwx------ 1 root root 64 Feb 27 14:50 0 -> /dev/pts/0
lrwx------ 1 root root 64 Feb 27 14:50 1 -> /dev/pts/0
lrwx------ 1 root root 64 Feb 27 14:49 2 -> /dev/pts/0

You can see that the process with the 324 pid doesn't hold the lock.

This information is required for proper dumping and restoring file
locks.

Signed-off-by: Andrey Vagin 
Cc: Jonathan Corbet 
Cc: Alexander Viro 
Acked-by: Jeff Layton 
Acked-by: "J. Bruce Fields" 
Acked-by: Cyrill Gorcunov 
Cc: Pavel Emelyanov 
Cc: Joe Perches 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds