mirror of
https://github.com/cloud-hypervisor/cloud-hypervisor.git
synced 2025-01-01 02:25:19 +00:00
53caa565bb
When freeing memory sometimes glibc will attempt to read "/proc/sys/vm/overcommit_memory" to find out how it should release the blocks. This happens sporadically with Cloud Hypervisor but has been seen in use. It is not necessary to add the read() syscall to the list as it is already included in the virtio devices common set. Similarly the vCPU and vmm threads already have both these in the allowed list. Fixes: #3609 Signed-off-by: Rob Bradford <robert.bradford@intel.com> |
||
|---|---|---|
| .. | ||
| transport | ||
| vhost_user | ||
| vsock | ||
| balloon.rs | ||
| block.rs | ||
| console.rs | ||
| device.rs | ||
| epoll_helper.rs | ||
| iommu.rs | ||
| lib.rs | ||
| mem.rs | ||
| net.rs | ||
| pmem.rs | ||
| rng.rs | ||
| seccomp_filters.rs | ||
| thread_helper.rs | ||
| watchdog.rs | ||