crosvm/seccomp/x86_64
Daniel Verkamp 5656c124af devices: block: fix seccomp failures from free()
It looks like free() will sometimes try to open
/proc/sys/vm/overcommit_memory in order to decide whether to return
freed heap memory to the kernel; change the seccomp filter to fail the
open syscalls with an error code (ENOENT) rather than killing the
process.

Also allow madvise to free memory for the same free() codepath.

BUG=chromium:888212
TEST=Run fio loop test on kevin

Change-Id: I1c27b265b822771f76b7d9572d9759476770000e
Signed-off-by: Daniel Verkamp <dverkamp@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/1305756
Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com>
Reviewed-by: Dylan Reid <dgreid@chromium.org>
2018-10-31 12:42:43 -07:00
..
9p_device.policy crosvm: add openat to seccomp 2018-10-21 05:25:01 -07:00
9s.policy crosvm: add getpid and prlimit to seccomp 2018-10-23 02:55:29 -07:00
balloon_device.policy balloon: Implement device policy 2018-07-27 15:29:07 -07:00
block_device.policy devices: block: fix seccomp failures from free() 2018-10-31 12:42:43 -07:00
gpu_device.policy crosvm: add openat to seccomp 2018-10-21 05:25:01 -07:00
net_device.policy devices: use PollContext for all virtio deivces 2018-04-05 15:20:42 -07:00
rng_device.policy devices: use PollContext for all virtio deivces 2018-04-05 15:20:42 -07:00
vhost_net_device.policy devices: use PollContext for all virtio deivces 2018-04-05 15:20:42 -07:00
vhost_vsock_device.policy devices: use PollContext for all virtio deivces 2018-04-05 15:20:42 -07:00
wl_device.policy seccomp: whitelist connect for wl_device 2018-09-20 15:00:24 -07:00