summaryrefslogtreecommitdiffstats
path: root/security/yama
diff options
context:
space:
mode:
authorGabriel Krisman Bertazi <krisman@collabora.com>2021-10-25 21:27:22 +0200
committerJan Kara <jack@suse.cz>2021-10-27 12:33:29 +0200
commite0462f91d24756916fded4313d508e0fc52f39c9 (patch)
tree6d28bf1033eb7fba4eaec6478d2b162cd0fc3b47 /security/yama
parentfanotify: Split fsid check from other fid mode checks (diff)
downloadlinux-e0462f91d24756916fded4313d508e0fc52f39c9.tar.xz
linux-e0462f91d24756916fded4313d508e0fc52f39c9.zip
inotify: Don't force FS_IN_IGNORED
According to Amir: "FS_IN_IGNORED is completely internal to inotify and there is no need to set it in i_fsnotify_mask at all, so if we remove the bit from the output of inotify_arg_to_mask() no functionality will change and we will be able to overload the event bit for FS_ERROR." This is done in preparation to overload FS_ERROR with the notification mechanism in fanotify. Link: https://lore.kernel.org/r/20211025192746.66445-8-krisman@collabora.com Suggested-by: Amir Goldstein <amir73il@gmail.com> Reviewed-by: Amir Goldstein <amir73il@gmail.com> Reviewed-by: Jan Kara <jack@suse.cz> Signed-off-by: Gabriel Krisman Bertazi <krisman@collabora.com> Signed-off-by: Jan Kara <jack@suse.cz>
Diffstat (limited to 'security/yama')
0 files changed, 0 insertions, 0 deletions