Frederick Mayle ef70f71256 cros_async: fix io at current file pos for io_uring ... The `ReadAsync` and `WriteAsync` traits accept file offsets as an `Option<u64>`. The epoll executor interprets `None` as "current file position" and the io_uring executor interprets `None` as position zero. This change updates the io_uring executor in favor of the epoll executor behavior. It is important to differentiate between position zero and "current file position" when you don't know whether a file is seekable. For example, console and serial devices should support both types of files as input. BUG=b:243198718 TEST=presubmit --all Change-Id: I01634e6bbdff352c0a6055419d0fafd10c0c40a6 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3841945 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Steven Moreland <smoreland@google.com> Reviewed-by: Takaya Saeki <takayas@chromium.org>		2022-09-30 20:32:02 +00:00
..
bindings.rs	bindgen: update bindings to Linux 5.15	2022-09-14 22:09:30 +00:00
lib.rs	Update all copyright headers to match new style	2022-09-13 18:41:29 +00:00
syscalls.rs	Update all copyright headers to match new style	2022-09-13 18:41:29 +00:00
uring.rs	cros_async: fix io at current file pos for io_uring	2022-09-30 20:32:02 +00:00