diff options
author | Amir Goldstein <amir73il@gmail.com> | 2018-10-04 00:25:33 +0300 |
---|---|---|
committer | Jan Kara <jack@suse.cz> | 2018-10-04 14:28:02 +0300 |
commit | 007d1e8395eaa59b0e7ad9eb2b53a40859446a88 (patch) | |
tree | ba3cafc48e79f3489f5faccfd5935cf2141f76f9 /CREDITS | |
parent | b723a7911d028fb55f67a63c4c4d895f72e059d4 (diff) | |
download | linux-007d1e8395eaa59b0e7ad9eb2b53a40859446a88.tar.xz |
fsnotify: generalize handling of extra event flags
FS_EVENT_ON_CHILD gets a special treatment in fsnotify() because it is
not a flag specifying an event type, but rather an extra flags that may
be reported along with another event and control the handling of the
event by the backend.
FS_ISDIR is also an "extra flag" and not an "event type" and therefore
desrves the same treatment. With inotify/dnotify backends it was never
possible to set FS_ISDIR in mark masks, so it did not matter.
With fanotify backend, mark adding code jumps through hoops to avoid
setting the FS_ISDIR in the commulative object mask.
Separate the constant ALL_FSNOTIFY_EVENTS to ALL_FSNOTIFY_FLAGS and
ALL_FSNOTIFY_EVENTS, so the latter can be used to test for specific
event types.
Signed-off-by: Amir Goldstein <amir73il@gmail.com>
Signed-off-by: Jan Kara <jack@suse.cz>
Diffstat (limited to 'CREDITS')
0 files changed, 0 insertions, 0 deletions