mirrors/crosvm
1
0
Fork 0
mirror of https://chromium.googlesource.com/crosvm/crosvm synced 2025-01-28 19:29:20 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
No description
31 commits 607 branches 2 tags 234 MiB
Rust 95.5%
Python 2%
C 1.7%
Shell 0.5%
Find a file
Dylan Reid 0584fe9fb2 Limit types that can be read from guest memory 
Not all types are safe to read from guest memory.  Any type with a
reference or pointer will be initialized to random bits that don't refer
to a valid address.  This can cause dangling pointer and general
unsafe behavior.

To fix this, limit types that can be read with read_obj to those that
implement the unsafe trait `DataInit`.  Provide implementations of
`DataInit` for intrinsic types that are obviously safe to initialize
with random data.

Implement the needed traits for bootparam types as they are read from
the kernel image directly.

Change-Id: I1040f5bc1b2fc4c58c87d8a2ce3f618edcf6f9b1
Signed-off-by: Dylan Reid <dgreid@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/540750
Reviewed-by: Zach Reizner <zachr@chromium.org>
2017-06-27 00:20:33 -07:00
data_model Add data_model with DataInit trait 2017-06-26 15:28:36 -07:00
io_jail io_jail: Add a wrapper around minijail 2017-05-25 12:25:27 -07:00
kernel_loader sys_util: Add guest_memory 2017-05-25 22:51:14 -07:00
kvm sys_util: Add guest_memory 2017-05-25 22:51:14 -07:00
kvm_sys kvm-sys: rename to kvm_sys 2017-05-02 05:20:27 -07:00
src/hw crosvm: add virtio MMIO transport module 2017-06-01 23:49:24 -07:00
sys_util Limit types that can be read from guest memory 2017-06-27 00:20:33 -07:00
syscall_defines syscall_defines: Add linux syscall defines. 2017-05-29 21:49:05 -07:00
x86_64 Limit types that can be read from guest memory 2017-06-27 00:20:33 -07:00
.gitignore gitignore: Remove Cargo.lock 2017-06-17 01:12:44 -07:00
LICENSE add LICENSE and README 2017-04-17 14:06:21 -07:00
README.md add LICENSE and README 2017-04-17 14:06:21 -07:00

README.md

Chrome OS KVM

This component, known as crosvm, runs untrusted operating systems along with virtualized devices. No actual hardware is emulated. This only runs VMs through the Linux's KVM interface. What makes crosvm unique is a focus on safety within the programming language and a sandbox around the virtual devices to protect the kernel from attack in case of an exploit in the devices.

Overview

The crosvm source code is organized into crates, each with their own unit tests. These crates are:

  • kvm-sys low-level (mostly) auto-generated structures and constants for using KVM
  • kvm unsafe, low-level wrapper code for using kvm-sys
  • crosvm the top-level binary front-end for using crosvm

Usage

Currently there is no front-end, so the best you can do is run cargo test in each crate.