Idan Raiter cbf1e0c61b devices: stop resetting ReadNotifiers in vhost user ... Upstreaming a fix from nkgold@ for the following issue: ReadNotifiers shouldn't ever be reset as their state is managed by the type that exposed the notifier (e.g. StreamChannel). Resetting it can lead to lose notifications. idanr@ discovered that EventAsync::clone_raw was creating a regular EventAsync (e.g. with reset), and it was being used with read notifiers. This CL replaces clone_raw with a new factory that produces `without_reset` EventAsyncs. BUG=b:253255209 TEST=presubmit, downstream Change-Id: I0b9de2f12cc3597ba05a8ac108f4cd0a8e726b3f Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3960857 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Commit-Queue: Idan Raiter <idanr@google.com>		2022-10-19 17:13:15 +00:00
..
src	devices: stop resetting ReadNotifiers in vhost user	2022-10-19 17:13:15 +00:00
Cargo.toml	Adding missing # provided by ebuild to Cargo.tomls	2022-10-14 16:42:38 +00:00