crosvm rename aarch64 seccomp to arm |
||
Issue descriptioncrosvm names it's seccomp policy aarch64 but it's really for the 32-bit syscalls, let's make it more consistent
,
Jul 24
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/platform/crosvm/+/b847858e66d58a3bf7506f43f1a22781014a527e commit b847858e66d58a3bf7506f43f1a22781014a527e Author: Sonny Rao <sonnyrao@chromium.org> Date: Tue Jul 24 04:04:38 2018 seccomp: rename aarch64 -> arm These policies are not for aarch64 but use the 32-bit system calls. We call it aarch64 support because that's what we're targetting for the guest kernel, but it doesn't really make any sense to call the seccomp policies aarch64 when we're building a 32-bit binary. We can add real aarch64 seccomp policies when we start building a aarch64 crosvm binary. BUG= chromium:866197 TEST=emerge-kevin crosvm, run vm_CrosVmStart CQ-DEPEND=CL:1145903 Change-Id: I7c5e70fbc127e4209ed392cfcf10ea36a6dd4b2c Reviewed-on: https://chromium-review.googlesource.com/1145909 Commit-Ready: Sonny Rao <sonnyrao@chromium.org> Tested-by: Sonny Rao <sonnyrao@chromium.org> Reviewed-by: Stephen Barber <smbarber@chromium.org> Reviewed-by: Zach Reizner <zachr@chromium.org> [rename] https://crrev.com/b847858e66d58a3bf7506f43f1a22781014a527e/seccomp/arm/block_device.policy [rename] https://crrev.com/b847858e66d58a3bf7506f43f1a22781014a527e/seccomp/arm/vhost_vsock_device.policy [rename] https://crrev.com/b847858e66d58a3bf7506f43f1a22781014a527e/seccomp/arm/net_device.policy [rename] https://crrev.com/b847858e66d58a3bf7506f43f1a22781014a527e/seccomp/arm/rng_device.policy [rename] https://crrev.com/b847858e66d58a3bf7506f43f1a22781014a527e/seccomp/arm/wl_device.policy [rename] https://crrev.com/b847858e66d58a3bf7506f43f1a22781014a527e/seccomp/arm/balloon_device.policy [rename] https://crrev.com/b847858e66d58a3bf7506f43f1a22781014a527e/seccomp/arm/vhost_net_device.policy
,
Jul 24
|
||
►
Sign in to add a comment |
||
Comment 1 by bugdroid1@chromium.org
, Jul 24