https://bugs.kde.org/show_bug.cgi?id=353874
--- Comment #26 from Oded Arbel <o...@geek.co.il> --- (In reply to Méven from comment #25) > The API does need CAP_SYS_ADMIN. This was indeed true, up until Linux 5.12: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/fs/notify/fanotify/fanotify_user.c?h=v5.12#n923 Since Linux 5.13, `CAP_SYS_ADMIN` is no longer required and instead just limits the flags you can use and the behavior you can expect: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/fs/notify/fanotify/fanotify_user.c?h=v5.13#n1044 With 5.13 and later, without `CAP_SYS_ADMIN` you cannot set fanotify for filesystem/mount wide marks and you can only get events with a file descriptor (that you can use, AFAIU): https://patchwork.kernel.org/project/linux-fsdevel/patch/20210524135321.2190062-1-amir7...@gmail.com/ I believe this should still be good enough for Baloo's purposes, as we are only expecting Baloo to use FAN_MARK_INODE for directories listed "File Search" configuration. -- You are receiving this mail because: You are watching all bug changes.
