locks: report l_pid as -1 for FL_FILE_PVT locks
authorJeff Layton <jlayton@redhat.com>
Mon, 3 Feb 2014 17:13:09 +0000 (12:13 -0500)
committerJeff Layton <jlayton@redhat.com>
Mon, 31 Mar 2014 12:24:42 +0000 (08:24 -0400)
commit3fd80cddc6af5ba53244514a61450d4b30a9fb9d
treecbca546dae6bcace6b933ef42130c7d3aa7ab2ca
parentc918d42a27a9be0d78be490997d16d79cd5b9193
locks: report l_pid as -1 for FL_FILE_PVT locks

FL_FILE_PVT locks are no longer tied to a particular pid, and are
instead inheritable by child processes. Report a l_pid of '-1' for
these sorts of locks since the pid is somewhat meaningless for them.

This precedent comes from FreeBSD. There, POSIX and flock() locks can
conflict with one another. If fcntl(F_GETLK, ...) returns a lock set
with flock() then the l_pid member cannot be a process ID because the
lock is not held by a process as such.

Acked-by: J. Bruce Fields <bfields@fieldses.org>
Signed-off-by: Jeff Layton <jlayton@redhat.com>
fs/locks.c
This page took 0.027367 seconds and 5 git commands to generate.