commit | cb3749e6327e26f9f685d76e9f0c3ceae146b717 | [log] [tgz] |
---|---|---|
author | Daniel Verkamp <dverkamp@chromium.org> | Wed Feb 09 12:36:34 2022 -0800 |
committer | Commit Bot <commit-bot@chromium.org> | Fri Feb 11 19:40:28 2022 +0000 |
tree | eed334a7115595e3526035116c813ddbce58aeff | |
parent | 5f46e21c0246cabf3161b62f40c988b7096515be [diff] |
devices: xhci: allow statx syscall on x86_64 Recent builds (starting R100.14501.0.0) crash when attaching a USB device to the Linux VM due to calling the statx syscall, which was missing from the seccomp policy. stat was already allowed, so add statx as well to prevent the crash. The change is likely due to the upgrade of the Rust toolchain in the Chrome OS SDK (https://crrev.com/c/3439725), which landed in this build. This was already allowed on arm/aarch64, so no other changes are required. BUG=b:218565401 TEST=Attach USB device to crosvm on hatch Change-Id: Ia3a383429a839c68b44040f4b99c990a1f1f8e9d Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3448188 Reviewed-by: Long Cheng <lgcheng@google.com> Reviewed-by: Dmitry Torokhov <dtor@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Reviewed-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Daniel Verkamp <dverkamp@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.