diff options
author | Sonny Rao <sonnyrao@chromium.org> | 2018-03-01 19:49:31 -0800 |
---|---|---|
committer | chrome-bot <chrome-bot@chromium.org> | 2018-03-02 15:47:18 -0800 |
commit | 0a404b8a0ea52344024e61c4631a328d49af9a1e (patch) | |
tree | 514c959edaa166f94b4a869b91874fec07933326 /Cargo.lock | |
parent | 505c6f98881e8998334d3f577334dd1570bca8d0 (diff) | |
download | crosvm-0a404b8a0ea52344024e61c4631a328d49af9a1e.tar crosvm-0a404b8a0ea52344024e61c4631a328d49af9a1e.tar.gz crosvm-0a404b8a0ea52344024e61c4631a328d49af9a1e.tar.bz2 crosvm-0a404b8a0ea52344024e61c4631a328d49af9a1e.tar.lz crosvm-0a404b8a0ea52344024e61c4631a328d49af9a1e.tar.xz crosvm-0a404b8a0ea52344024e61c4631a328d49af9a1e.tar.zst crosvm-0a404b8a0ea52344024e61c4631a328d49af9a1e.zip |
sys_util: fix issue in ppoll on 32-bit architectures
I ran into an issue on ARM where ppoll() was returning EINVAL and it was becuase our timespec value sent to ppoll contained a negative value for tv_sec. We need to use the correct type when determining the max value. BUG=chromium:797868 TEST=./build_test passes on all architectures TEST=crosvm runs on caroline Change-Id: I7f8818e5f93e0327fd9facefb5032f7c5fb00ea0 Reviewed-on: https://chromium-review.googlesource.com/945111 Commit-Ready: Sonny Rao <sonnyrao@chromium.org> Tested-by: Sonny Rao <sonnyrao@chromium.org> Reviewed-by: Zach Reizner <zachr@chromium.org>
Diffstat (limited to 'Cargo.lock')
0 files changed, 0 insertions, 0 deletions