summaryrefslogtreecommitdiffstats
path: root/fs/fcntl.c
diff options
context:
space:
mode:
authorJeff Layton <jlayton@redhat.com>2014-02-03 12:13:09 -0500
committerJeff Layton <jlayton@redhat.com>2014-03-31 08:24:42 -0400
commit3fd80cddc6af5ba53244514a61450d4b30a9fb9d (patch)
treecbca546dae6bcace6b933ef42130c7d3aa7ab2ca /fs/fcntl.c
parentc918d42a27a9be0d78be490997d16d79cd5b9193 (diff)
downloadop-kernel-dev-3fd80cddc6af5ba53244514a61450d4b30a9fb9d.zip
op-kernel-dev-3fd80cddc6af5ba53244514a61450d4b30a9fb9d.tar.gz
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>
Diffstat (limited to 'fs/fcntl.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud