Re: [PATCH v2] fanotify reports the thread id of the event trigger

2018-09-18 Thread Amir Goldstein
On Tue, Sep 18, 2018 at 12:50 PM Nixiaoming wrote: > > On Tue, Sep 18, 2018 3:07 PM Amir Goldstein > >On Tue, Sep 18, 2018 at 6:01 AM Nixiaoming wrote: > >> > >> On Mon, Sep 17, 2018 11:51 PM Amir Goldstein wrote: > >> >On Mon, Sep 17, 2018 at 6:05 PM nixiaoming wrote: > >... > >> >> diff

Re: [PATCH v2] fanotify reports the thread id of the event trigger

2018-09-18 Thread Amir Goldstein
On Tue, Sep 18, 2018 at 12:50 PM Nixiaoming wrote: > > On Tue, Sep 18, 2018 3:07 PM Amir Goldstein > >On Tue, Sep 18, 2018 at 6:01 AM Nixiaoming wrote: > >> > >> On Mon, Sep 17, 2018 11:51 PM Amir Goldstein wrote: > >> >On Mon, Sep 17, 2018 at 6:05 PM nixiaoming wrote: > >... > >> >> diff

RE: [PATCH v2] fanotify reports the thread id of the event trigger

2018-09-18 Thread Nixiaoming
On Tue, Sep 18, 2018 3:07 PM Amir Goldstein >On Tue, Sep 18, 2018 at 6:01 AM Nixiaoming wrote: >> >> On Mon, Sep 17, 2018 11:51 PM Amir Goldstein wrote: >> >On Mon, Sep 17, 2018 at 6:05 PM nixiaoming wrote: >... >> >> diff --git a/include/linux/fsnotify_backend.h >> >>

RE: [PATCH v2] fanotify reports the thread id of the event trigger

2018-09-18 Thread Nixiaoming
On Tue, Sep 18, 2018 3:07 PM Amir Goldstein >On Tue, Sep 18, 2018 at 6:01 AM Nixiaoming wrote: >> >> On Mon, Sep 17, 2018 11:51 PM Amir Goldstein wrote: >> >On Mon, Sep 17, 2018 at 6:05 PM nixiaoming wrote: >... >> >> diff --git a/include/linux/fsnotify_backend.h >> >>

Re: [PATCH v2] fanotify reports the thread id of the event trigger

2018-09-18 Thread Amir Goldstein
On Tue, Sep 18, 2018 at 6:01 AM Nixiaoming wrote: > > On Mon, Sep 17, 2018 11:51 PM Amir Goldstein wrote: > >On Mon, Sep 17, 2018 at 6:05 PM nixiaoming wrote: ... > >> diff --git a/include/linux/fsnotify_backend.h > >> b/include/linux/fsnotify_backend.h > >> index b8f4182..44c659f 100644 > >>

Re: [PATCH v2] fanotify reports the thread id of the event trigger

2018-09-18 Thread Amir Goldstein
On Tue, Sep 18, 2018 at 6:01 AM Nixiaoming wrote: > > On Mon, Sep 17, 2018 11:51 PM Amir Goldstein wrote: > >On Mon, Sep 17, 2018 at 6:05 PM nixiaoming wrote: ... > >> diff --git a/include/linux/fsnotify_backend.h > >> b/include/linux/fsnotify_backend.h > >> index b8f4182..44c659f 100644 > >>

RE: [PATCH v2] fanotify reports the thread id of the event trigger

2018-09-17 Thread Nixiaoming
On Mon, Sep 17, 2018 11:51 PM Amir Goldstein wrote: >On Mon, Sep 17, 2018 at 6:05 PM nixiaoming wrote: >> >> In order to identify which thread triggered the event in the >> multi-threaded program, add the FAN_EVENT_INFO_TID tag in fanotify_init > >According to code and man page this is a 'flag'

RE: [PATCH v2] fanotify reports the thread id of the event trigger

2018-09-17 Thread Nixiaoming
On Mon, Sep 17, 2018 11:51 PM Amir Goldstein wrote: >On Mon, Sep 17, 2018 at 6:05 PM nixiaoming wrote: >> >> In order to identify which thread triggered the event in the >> multi-threaded program, add the FAN_EVENT_INFO_TID tag in fanotify_init > >According to code and man page this is a 'flag'

Re: [PATCH v2] fanotify reports the thread id of the event trigger

2018-09-17 Thread Amir Goldstein
On Mon, Sep 17, 2018 at 6:05 PM nixiaoming wrote: > > In order to identify which thread triggered the event in the > multi-threaded program, add the FAN_EVENT_INFO_TID tag in fanotify_init According to code and man page this is a 'flag' not a 'tag' Please stick to existing terminology. > to

Re: [PATCH v2] fanotify reports the thread id of the event trigger

2018-09-17 Thread Amir Goldstein
On Mon, Sep 17, 2018 at 6:05 PM nixiaoming wrote: > > In order to identify which thread triggered the event in the > multi-threaded program, add the FAN_EVENT_INFO_TID tag in fanotify_init According to code and man page this is a 'flag' not a 'tag' Please stick to existing terminology. > to