mirror of
https://chromium.googlesource.com/crosvm/crosvm
synced 2024-11-24 12:34:31 +00:00
ef70f71256
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> |
||
|---|---|---|
| .. | ||
| src | ||
| bindgen.sh | ||
| Cargo.toml | ||