jeandudey / tokio-udev Goto Github PK

View Code? Open in Web Editor NEW

23.0 2.0 3.0 95 KB

Asynchronous udev hotplug monitor using Tokio and Mio.

Home Page: https://docs.rs/tokio-udev

Rust 72.12% Scheme 27.88%

tokio mio udev libudev hotplug async asynchronous

tokio-udev's Introduction

`tokio-udev`

Non-blocking/asynchronous mio & tokio support for udev device events

Documentation

Minimum Supported Rust Version

The crates are guaranteed to compile on stable Rust 1.56. It might compile with older versions but that may change in any new patch release.

License

Licensed under either of

Apache License, Version 2.0 (LICENSE-APACHE or http://www.apache.org/licenses/LICENSE-2.0)
MIT License (LICENSE-MIT or http://opensource.org/licenses/MIT)

at your option.

Contribution

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.

tokio-udev's People

Contributors

Stargazers

Watchers

Forkers

xentec ids1024 sjoerdsimons

tokio-udev's Issues

Re-export Enumerator

So, I'm writing a USB API, and I'd like udev::Enumerator to be exported so I can rely on just tokio-udev instead of udev.

Additionally, it'd be nice to have Enumerator wrapped in a Stream despite not being asynchronous; that way if you wanted to run code on a new device, you could chain a stream over the wrapped Enumerator and MonitorSocket.

Tag new release of `tokio-udev`

ff68101 the following commit fixes a crucial issue which the downstream project https://GitHub.com/waycrate/swhkd depends on. If a release could be tagged, it would be significantly helpful for us.

Events were blocked while poll next

While using Tokio-udev to monitor usb disk plugin events, We found that not all the events can be polled at sametime, but until plugin/unplugin a usb disk next time.

This issuse can be easily reproduced by partition a usb disk to 4 or more partitions.

Update to mio 0.7

Mio 0.7 has been available for a while, lets wait for tokio to update from mio-0.6 to mio-0.7.

EventType not exported

It appears that EventType - necessary for using Event's event_type() - isn't imported/exported from tokio-udev or mio-udev.

Edit: not sure if this is normal practice, so my apologies if this is just noise.

`tokio-udev` v0.8 and v0.7 are the same

The last release of tokio-udev is missing commit 8d9b695.

Incorrect Send/Sync implementation of tokio_udev::MonitorSocket.

The Send and Sync implementation of tokio_udev::MonitorSocket is incorrect and can be used to trigger undefined behavior:

Create a MonitorSocket and poll it until an Event is returned.
Send the monitor to another thread and poll it until an Event is returned.
On both threads, start and endless loop where you clone the returned event drop the clone again.

This results in unsynchronized calls to udev_ref and udev_unref on the same udev instance. This is not allowed by libudev and triggers undefined behavior.

In particular, no type that contains pointers to libudev objects can possibly be Send or Sync.