Hello Amir, On 11/17/18 5:32 PM, Amir Goldstein wrote: > From: nixiaoming <nixiaoming@xxxxxxxxxx> > > fanotify_init.2 add new flags FAN_REPORT_TID > fanotify.7 update description of member pid in struct fanotify_event_metadata > > [amir: renamed flag to FAN_REPORT_TID and editing] > > Signed-off-by: nixiaoming <nixiaoming@xxxxxxxxxx> > Signed-off-by: Amir Goldstein <amir73il@xxxxxxxxx> > --- > man2/fanotify_init.2 | 4 ++++ > man7/fanotify.7 | 8 +++++++- > 2 files changed, 11 insertions(+), 1 deletion(-) > > diff --git a/man2/fanotify_init.2 b/man2/fanotify_init.2 > index e3a0b9854..94d0292f6 100644 > --- a/man2/fanotify_init.2 > +++ b/man2/fanotify_init.2 > @@ -142,6 +142,10 @@ Remove the limit of 8192 marks. > Use of this flag requires the > .B CAP_SYS_ADMIN > capability. > +.TP > +.BR FAN_REPORT_TID " (since Linux 4.20)" > +.\" commit d0a6a87e40da49cfc7954c491d3065a25a641b29 > +Report thread id (TID) instead of process id (PID). > .PP > The > .I event_f_flags > diff --git a/man7/fanotify.7 b/man7/fanotify.7 > index ec5532f55..c52aadeda 100644 > --- a/man7/fanotify.7 > +++ b/man7/fanotify.7 > @@ -223,7 +223,13 @@ Hence, when the receiver of the fanotify event accesses the notified file or > directory using this file descriptor, no additional events will be created. > .TP > .I pid > -This is the ID of the process that caused the event. > +If flag > +.B FAN_REPORT_TID > +was set in > +.BR fanotify_init (2), > +this is the TID of the thread that caused the event. > +Otherwise, this the PID of the process that caused the event. > +.PP > A program listening to fanotify events can compare this PID > to the PID returned by > .BR getpid (2), Thanks. I've applied this patch. Cheers, Michael -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/
