Skip to content

Release of version 0.3.1

Latest
Compare
Choose a tag to compare
@pantsman0 pantsman0 released this 09 Feb 04:08
22f4dc4

The following changes have occured since the previous release to crates.io (0.2.10)

[0.3.1] - 2024-02-08

No other changes

[0.3.1-rc3] - 2024-02-08

Implement Send, Sync, and Clone for Fanotify.

Added

Added implementations of the Send, Sync, and Clone traits for better ergonomics on the Fanotify type.

[0.3.1-rc2] - 2024-02-05

Rename Fanotify functions and stop eating registration errors.

Added

Added FanotifyBuilder to provide finer-grained control on what options are supplied to the libc call without directly using the low_level methods.

Changed

Rename Fanotify::new_with_blocking and Fanotify::new_with_nonblocking
The above functions now bubble up registration errors

[0.3.1-rc1] - 2024-02-04

Big update and refactor. The overral structure remains the same, but includes a number of fixes included in outstanding PRs. The update have been checked against current test cases and the PoC, but need review before release.

Added

Implemented AsFd for Fanotify to allow borrowing of the internal file descriptor (e.g. for polling)

Changed

Widened the implementation of FanotifyPath to all implementors of AsRef<OsStr>, but removed the direct implementation for String due to conflict.
Update dependencies, and removed the dependency on lazy_static.
Updated the crate to 2021 edition.
Changed type of PID in the Event type as pid_t is generally implemented as int in libc implementations.
Changed to_fan_class to to copy instead of borrow as the type is Copy.
Renamed low_level::fanotify_response to low_level::FanotifyResponse to keep with Rust's naming convention.
Removed crate definitions of some library flags, and replaced with re-exports from libc.
Removed setting that forced inclusion of debug symbols in release mode.

Fixed

Fixed the type for calling fanotify_mark on aarch64