diff options
| author | Amir Goldstein <[email protected]> | 2024-01-09 20:22:45 +0200 |
|---|---|---|
| committer | Christian Brauner <[email protected]> | 2024-01-12 15:34:50 +0100 |
| commit | 7ea26f9460c6c76b1d6e36f39fce34b16cb88300 (patch) | |
| tree | 0e738d825c25ccc6a032d786b0229feefaac132c /tools/perf/scripts/python/failed-syscalls-by-pid.py | |
| parent | 70d201a40823acba23899342d62bc2644051ad2e (diff) | |
fsnotify: compile out fsnotify permission hooks if !FANOTIFY_ACCESS_PERMISSIONS
The depency of FANOTIFY_ACCESS_PERMISSIONS on SECURITY made sure that
the fsnotify permission hooks were never called when SECURITY was
disabled.
Moving the fsnotify permission hook out of the secutiy hook broke that
optimisation.
Reported-and-tested-by: Jens Axboe <[email protected]>
Closes: https://lore.kernel.org/linux-fsdevel/[email protected]/
Fixes: d9e5d31084b0 ("fsnotify: optionally pass access range in file permission hooks")
Signed-off-by: Amir Goldstein <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Reviewed-by: Jan Kara <[email protected]>
Signed-off-by: Christian Brauner <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/failed-syscalls-by-pid.py')
0 files changed, 0 insertions, 0 deletions