cpu / rfanotify Goto Github PK

Linux 5.1 added many of inotify's directory based events to fanotify (e.g. FAN_ATTRIB, FAN_CREATE, etc). It also added a new fanotify_init flag FAN_REPORT_FID that allows receiving an additional structure beyond the base fanotify_event_metadata structure that contains information about the filesystem object correlated with an event (e.g. a monitored directory or mount).

Since my forked libc and nix crates used by this project do not yet implement any of these updates that work will need to be completed first. Afterwards it will be possible to port the fanotify_fid.c example C program included in release 5.05 of the Linux man-pages project.

The original fanotify example program that serves the basis of the rfanotify port uses poll on the fanotify descriptor in nonblocking mode. It also polls stdin to allow the user to quit gracefully by entering any input to stdin.

Presently rfanotify reads from the fanotify descriptor in a blocking fashion. It also doesn't read from stdin or offer any graceful exit, requiring the user to send a signal instead.

I should switch rfanotify to use InitFlags::FAN_NONBLOCK with Fanotify::init and implement an async approach to reading events and monitoring stdin. Since I'm super new to rust I punted on non-blocking I/O in the first version.