fanotify-rs
fanotify-rs copied to clipboard
The high-level/low-level implementation of Linux Fanotify.
Since Rust 1.28 (released in 2018), `std::mem::size_of` is *const*, so the value can be computed at compile time.
pid_t is defined as a signed integer in the Linux kernel: https://elixir.bootlin.com/linux/latest/source/tools/include/nolibc/nolibc.h#L132 As well as in Rust libraries like: https://docs.rs/libc/0.2.65/libc/type.pid_t.html To keep the compatibility with those, change the type of...
ARM architectures (like aarch64 or armv7) are by default defining `char` type as an unsigned integer. That fact was preventing fanotify-rs to compile on ARM. This change fixes it by...
Hi, this create looks neat. I like it :smiley: There is a piece of code that I don't quite understand. Can you explain a bit? https://github.com/ZhangLei-cn/fanotify-rs/blob/4987bc7f784330cc86cdba79e7a04f2f8aa27885/src/low_level.rs#L374-L389 There are two problems:...
The code here is from version 0.2.7, but the version available on crates.io is 0.2.10.
Hi dev, I see there is no implementation of `fanotify_event_info_fid`, are you planning to add it? If not, is there any workaround to that?
To be precise, - like 4 typos - a few missing dots at the ends of the sentences - a lot of missing backticks around the names of constants or...
This started as a debugging session where I was getting errors that were not getting handled properly (os error 13 on `fanotify_read`) which made me realise the `libc::read` error handling...
Due to a refactor done last year, this simple demo also needs adjustments to be working correctly