aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/net_dropmonitor.py
diff options
context:
space:
mode:
authorKonstantin Khorenko <[email protected]>2018-06-08 17:27:12 +0300
committerJeff Layton <[email protected]>2018-06-14 07:37:50 -0400
commit1cf8e5de4055f85383405a21a0a7c3c4348bf2ed (patch)
tree4dec4fc42e59f938a1aa6e01c29c7c85d2b623fa /tools/perf/scripts/python/net_dropmonitor.py
parent826d7bc9f013d01e92997883d2fd0c25f4af1f1c (diff)
fs/lock: show locks taken by processes from another pidns
Currently if we face a lock taken by a process invisible in the current pidns we skip the lock completely, but this 1) makes the output not that nice (root@vz7)/: cat /proc/${PID_A2}/fdinfo/3 pos: 4 flags: 02100002 mnt_id: 257 lock: (root@vz7)/: 2) makes it more difficult to debug issues with leaked flocks if you get error on lock, but don't see any locks in /proc/$id/fdinfo/$file Let's show information about such locks again as previously, but show zero in the owner pid field. After the patch: =============== (root@vz7)/:cat /proc/${PID_A2}/fdinfo/3 pos: 4 flags: 02100002 mnt_id: 295 lock: 1: FLOCK ADVISORY WRITE 0 b6:f8a61:529946 0 EOF Fixes: 9d5b86ac13c5 ("fs/locks: Remove fl_nspid and use fs-specific l_pid for remote locks") Signed-off-by: Konstantin Khorenko <[email protected]> Acked-by: Andrey Vagin <[email protected]> Reviewed-by: Benjamin Coddington <[email protected]> Signed-off-by: Jeff Layton <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/net_dropmonitor.py')
0 files changed, 0 insertions, 0 deletions