tree 401bc8d85e7228f868775269e6d97c3150f9a3a7
parent 4d92604cc90aa18bbbe0f6e23b7a9fdb612836d3
author Eric Paris <eparis@redhat.com> 1261103074 -0500
committer Eric Paris <eparis@redhat.com> 1280325541 -0400

fsnotify: add group priorities

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>