commit | eae6d2d3eafe04f9ad849a0abdf58f216d8d2dd2 | [log] [tgz] |
---|---|---|
author | Frederick Mayle <fmayle@google.com> | Thu Sep 12 11:05:36 2024 -0700 |
committer | Frederick Mayle <fmayle@google.com> | Thu Sep 12 11:13:58 2024 -0700 |
tree | ee2788ae2a7fef930303e5bef4a83191e4095fc9 | |
parent | 0f12175fe12d24f2cdb8d9a31afd90a5d1e77c9a [diff] |
virtmgr: disable disk file locking in crosvm crosvm calls `man 2 flock` on disk image files. It used to only call it on the "root" image, but now it calls it on all the nested images, e.g. the "component" files in a composite disk image. That isn't necessarily a bad thing, but the SELinux policies don't allow it. For example, some of the disk images used by Microdroid are labelled with the very generic "system_file" context. We should consider changing the policies, but, in meantime, disable locking isn't a big deal. Generally the files are either read-only at the FS level (and so the locking is mostly redundant) or are generated per VM images (and so no conflict is likely). Bug: 364645148, 330911976 Test: launch microdroid Change-Id: I5d64ee343d56620df4389c57dbbb99a57e2c3c8c
Android Virtualization Framework (AVF) provides secure and private execution environments for executing code. AVF is ideal for security-oriented use cases that require stronger isolation assurances over those offered by Android’s app sandbox.
Visit our public doc site to learn more about what AVF is, what it is for, and how it is structured. This repository contains source code for userspace components of AVF.
If you want a quick start, see the getting started guideline and follow the steps there.
For in-depth explanations about individual topics and components, visit the following links.
AVF components:
AVF APIs:
How-Tos: