cloud-hypervisor/vm-device/Cargo.toml

[package]
name = "vm-device"
version = "0.1.0"
authors = ["The Cloud Hypervisor Authors"]
edition = "2018"

[features]
default = []
kvm = ["vfio-ioctls/kvm"]

[dependencies]
anyhow = "1.0.42"
thiserror = "1.0.26"
serde = { version = "1.0.127", features = ["rc"] }
serde_derive = "1.0.127"
serde_json = "1.0.66"
vfio-ioctls = { git = "https://github.com/rust-vmm/vfio-ioctls", branch = "master", default-features = false }
vm-memory = { version = "0.6.0", features = ["backend-mmap"] }
vmm-sys-util = "0.8.0"
vm-device: Add new crate for virtio and VFIO agnostic traits The new crate vm-device is created here to host the definitions of traits not meant to be tied to virtio of VFIO specifically. We need to add a new trait to update external DMA mappings for devices, which is why the vm-device crate is the right fit for this. We can expect this crate to be extended later once the design gets approved from a rust-vmm perspective. In this specific use case, we can have some devices like VFIO or vhost-user ones requiring to be notified about mapping updates. This new trait ExternalDmaMapping will allow such devices to implement their own way to handle such event. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com> 2019-10-07 16:57:19 +00:00			`[package]`
			`name = "vm-device"`
			`version = "0.1.0"`
			`authors = ["The Cloud Hypervisor Authors"]`
			`edition = "2018"`

vmm, vm-device: make use of the kvm feature gate in vfio-ioctls The vfio-ioctls crate now contains a KVM feature gate. Make use of it in Cloud Hypervisor. That crate has two users. For the vmm crate is it straight-forward. For the vm-device crate, we introduce a KVM feature gate as well so that the vmm crate can pass on the configuration. Signed-off-by: Wei Liu <liuwe@microsoft.com> 2021-07-13 16:04:32 +00:00			`[features]`
			`default = []`
			`kvm = ["vfio-ioctls/kvm"]`

vm-device: Add new crate for virtio and VFIO agnostic traits The new crate vm-device is created here to host the definitions of traits not meant to be tied to virtio of VFIO specifically. We need to add a new trait to update external DMA mappings for devices, which is why the vm-device crate is the right fit for this. We can expect this crate to be extended later once the design gets approved from a rust-vmm perspective. In this specific use case, we can have some devices like VFIO or vhost-user ones requiring to be notified about mapping updates. This new trait ExternalDmaMapping will allow such devices to implement their own way to handle such event. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com> 2019-10-07 16:57:19 +00:00			`[dependencies]`
build: Use fixed versions in Cargo.toml files This doesn't really affect the build as we ship a Cargo.lock with fixed versions in. However for clarity it makes sense to use fixed versions throughout and let dependabot update them. Signed-off-by: Rob Bradford <robert.bradford@intel.com> 2021-08-06 09:11:40 +00:00			`anyhow = "1.0.42"`
			`thiserror = "1.0.26"`
			`serde = { version = "1.0.127", features = ["rc"] }`
			`serde_derive = "1.0.127"`
			`serde_json = "1.0.66"`
vmm, vm-device: make use of the kvm feature gate in vfio-ioctls The vfio-ioctls crate now contains a KVM feature gate. Make use of it in Cloud Hypervisor. That crate has two users. For the vmm crate is it straight-forward. For the vm-device crate, we introduce a KVM feature gate as well so that the vmm crate can pass on the configuration. Signed-off-by: Wei Liu <liuwe@microsoft.com> 2021-07-13 16:04:32 +00:00			`vfio-ioctls = { git = "https://github.com/rust-vmm/vfio-ioctls", branch = "master", default-features = false }`
build: Move from patched vm-memory version to released version Signed-off-by: Rob Bradford <robert.bradford@intel.com> 2021-08-06 07:46:17 +00:00			`vm-memory = { version = "0.6.0", features = ["backend-mmap"] }`
build: Use fixed versions in Cargo.toml files This doesn't really affect the build as we ship a Cargo.lock with fixed versions in. However for clarity it makes sense to use fixed versions throughout and let dependabot update them. Signed-off-by: Rob Bradford <robert.bradford@intel.com> 2021-08-06 09:11:40 +00:00			`vmm-sys-util = "0.8.0"`
vsock: vhost_user: vfio: Fix potential host memory overflow The vsock packets that we're building are resolving guest addresses to host ones and use the latter as raw pointers. If the corresponding guest mapped buffer spans across several regions in the guest, they will do so in the host as well. Since we have no guarantees that host regions are contiguous, it may lead the VMM into trying to access memory outside of its memory space. For now we fix that by ensuring that the guest buffers do not span across several regions. If they do, we error out. Ideally, we should enhance the rust-vmm memory model to support safe acces across host regions. Fixes CVE-2019-18960 Signed-off-by: Samuel Ortiz <sameo@linux.intel.com> 2019-12-12 13:08:34 +00:00