commit | 91019884bbe889b882c48e0901006306241c16c3 | [log] [tgz] |
---|---|---|
author | Keiichi Watanabe <keiichiw@chromium.org> | Thu Nov 18 00:34:09 2021 +0900 |
committer | Commit Bot <commit-bot@chromium.org> | Fri Nov 26 14:28:28 2021 +0000 |
tree | a5bf71b2987580ff2db8c2b6623ad3677d186a60 | |
parent | 2533dd15bf8b0aebcc7ac54b9862539538453b01 [diff] |
sys_util: Replace unsafe use of iovecs `sys_util::recv_iovecs_with_fds` was implemented as a safe function, but it was actually unsafe because it assumed that the caller would give a slice of `libc::iovec` where each `iov_base` points a valid memory region with `iov_len`. To make the function truly safe, it should take a slice of IoSliceMut instead. BUG=none TEST=cargo test in sys_util/vmm_vhost TEST=vhost-user block still works Change-Id: I45458ee4545af13ce7e0955fb67b3703b147e7df Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3288733 Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Keiichi Watanabe <keiichiw@chromium.org> Reviewed-by: Chirantan Ekbote <chirantan@chromium.org>
crosvm is a virtual machine monitor (VMM) based on Linux’s KVM hypervisor, with a focus on simplicity, security, and speed. crosvm is intended to run Linux guests, originally as a security boundary for running native applications on the Chrome OS platform. Compared to QEMU, crosvm doesn’t emulate architectures or real hardware, instead concentrating on paravirtualized devices, such as the virtio standard.
crosvm is currently used to run Linux/Android guests on Chrome OS devices.