commit | 5d0617cd8882efd70e776da8ca6f7aa8a519252e | [log] [tgz] |
---|---|---|
author | Daniel Verkamp <dverkamp@chromium.org> | Tue Feb 22 15:24:52 2022 -0800 |
committer | Commit Bot <commit-bot@chromium.org> | Wed Feb 23 19:23:31 2022 +0000 |
tree | da5351783e77a3e160115a22b5b8c54832febda3 | |
parent | 6dce4fa0d40dd11d4d65042384ec5f10eed21a60 [diff] |
seccomp: use common_device.policy in tpm_device.policy The TPM device was changed to manually include an edited subset of common_device.policy in commit 25a86d99cca8 ("tpm: Update tpm device policy to support libtpm2") because common_device.policy included rules for open and openat at the time, and the TPM device needed to override those rules. Now that common_device.policy no longer defines rules for open and openat, it is safe to include the common policy instead of duplicating it. BUG=None TEST=build with features=tpm and run with --software-tpm Change-Id: Ia79d63fcf2cd2c5303384f4d0607b3b543406098 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3482029 Reviewed-by: Dmitry Torokhov <dtor@chromium.org> Tested-by: kokoro <noreply+kokoro@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.