mirror of
https://github.com/torvalds/linux.git
synced 2024-12-07 11:31:41 +00:00
cb2d429faf
This introduces an ordering to fsnotify groups. With purely asynchronous notification based "things" implementing fsnotify (inotify, dnotify) ordering isn't particularly important. But if people want to use fsnotify for the basis of sycronous notification or blocking notification ordering becomes important. eg. A Hierarchical Storage Management listener would need to get its event before an AV scanner could get its event (since the HSM would need to bring the data in for the AV scanner to scan.) Typically asynchronous notification would want to run after the AV scanner made any relevant access decisions so as to not send notification about an event that was denied. Signed-off-by: Eric Paris <eparis@redhat.com> |
||
---|---|---|
.. | ||
fanotify_user.c | ||
fanotify.c | ||
Kconfig | ||
Makefile |