diff options
| author | Amir Goldstein <amir73il@gmail.com> | 2020-05-27 15:54:55 +0300 |
|---|---|---|
| committer | Jan Kara <jack@suse.cz> | 2020-05-27 18:55:54 +0200 |
| commit | f17936993af054b16725d0c54baa58115f9e052a (patch) | |
| tree | 8c0900fd6d54e2e5482eddc9e79d9a236e3dc7be /fs/notify | |
| parent | 444fc5cde64330661bf59944c43844e7d4c2ccd8 (diff) | |
| download | linux-stable-f17936993af054b16725d0c54baa58115f9e052a.tar.gz linux-stable-f17936993af054b16725d0c54baa58115f9e052a.tar.bz2 linux-stable-f17936993af054b16725d0c54baa58115f9e052a.zip | |
fanotify: turn off support for FAN_DIR_MODIFY
FAN_DIR_MODIFY has been enabled by commit 44d705b0370b ("fanotify:
report name info for FAN_DIR_MODIFY event") in 5.7-rc1. Now we are
planning further extensions to the fanotify API and during that we
realized that FAN_DIR_MODIFY may behave slightly differently to be more
consistent with extensions we plan. So until we finalize these
extensions, let's not bind our hands with exposing FAN_DIR_MODIFY to
userland.
Signed-off-by: Amir Goldstein <amir73il@gmail.com>
Signed-off-by: Jan Kara <jack@suse.cz>
Diffstat (limited to 'fs/notify')
| -rw-r--r-- | fs/notify/fanotify/fanotify.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/notify/fanotify/fanotify.c b/fs/notify/fanotify/fanotify.c index 5435a40f82be..c18459cea6f4 100644 --- a/fs/notify/fanotify/fanotify.c +++ b/fs/notify/fanotify/fanotify.c @@ -520,7 +520,7 @@ static int fanotify_handle_event(struct fsnotify_group *group, BUILD_BUG_ON(FAN_OPEN_EXEC != FS_OPEN_EXEC); BUILD_BUG_ON(FAN_OPEN_EXEC_PERM != FS_OPEN_EXEC_PERM); - BUILD_BUG_ON(HWEIGHT32(ALL_FANOTIFY_EVENT_BITS) != 20); + BUILD_BUG_ON(HWEIGHT32(ALL_FANOTIFY_EVENT_BITS) != 19); mask = fanotify_group_event_mask(group, iter_info, mask, data, data_type); |