diff options
author | 2014-02-03 12:13:09 -0500 | |
---|---|---|
committer | 2014-03-31 08:24:42 -0400 | |
commit | 3fd80cddc6af5ba53244514a61450d4b30a9fb9d (patch) | |
tree | cbca546dae6bcace6b933ef42130c7d3aa7ab2ca /tools/perf/scripts/python/export-to-postgresql.py | |
parent | locks: make /proc/locks show IS_FILE_PVT locks as type "FLPVT" (diff) | |
download | linux-dev-3fd80cddc6af5ba53244514a61450d4b30a9fb9d.tar.xz linux-dev-3fd80cddc6af5ba53244514a61450d4b30a9fb9d.zip |
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 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions