From f2116342e9b2ddc4d581496078a8b222330af90e Mon Sep 17 00:00:00 2001 From: Masatake YAMATO Date: Sat, 10 Sep 2022 02:09:01 +0900 Subject: [PATCH] lsfd: (man) write about PIDFD.* columns --- misc-utils/lsfd.1.adoc | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) diff --git a/misc-utils/lsfd.1.adoc b/misc-utils/lsfd.1.adoc index f782b83c21..20d9e981e5 100644 --- a/misc-utils/lsfd.1.adoc +++ b/misc-utils/lsfd.1.adoc @@ -217,6 +217,28 @@ Block device name resolved by `/proc/partition`. PID <``number``>:: PID of the process opening the file. +PIDFD.COMM <``string``>:: +Command of the process targeted by the pidfd. + +PIDFD.NSPID <``string``>:: +Value of NSpid field in ``/proc/``_pid_``/fdinfo/``_fd_ of the pidfd. ++ +Quoted from kernel/fork.c of Linux source tree: ++ +____ +If pid namespaces are supported then this function will also print +the pid of a given pidfd refers to for all descendant pid namespaces +starting from the current pid namespace of the instance, i.e. the +Pid field and the first entry in the NSpid field will be identical. +... +Note that this differs from the Pid and NSpid fields in +/proc//status where Pid and NSpid are always shown relative to +the pid namespace of the procfs instance. +____ + +PIDFD.PID <``number``>:: +PID of the process targeted by the pidfd. + POS <``number``>:: File position. -- 2.47.3