History | View | Annotate | Download (7.6 kB)
seccomp: no need to check arch in syscall whitelist
v2 update:- set libseccomp 2.1.0 as requirement on configure script.
Since libseccomp 2.0 there's no need to check the architecture typeanymore.
Signed-off-by: Eduardo Otubo <otubo@linux.vnet.ibm.com>...
seccomp: removing unused syscalls gtom whitelist
v3 update: - reincluding getrlimit(), it is used by Xen.
v2 update: - reincluding setrlimit(), it is used by Xen.
Signed-off-by: Eduardo Otubo <otubo@linux.vnet.ibm.com>Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>...
seccomp: add the asynchronous I/O syscalls to the whitelist
In order to enable the asynchronous I/O functionality when using theseccomp sandbox we need to add the associated syscalls to thewhitelist.
Signed-off-by: Paul Moore <pmoore@redhat.com>Reviewed-by: Corey Bryant <coreyb@linux.vnet.ibm.com>...
softmmu: move include files to include/sysemu/
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
seccomp: adding new syscalls (bugzilla 855162)
According to the bug 8551620 - there's the need of adding new syscallsto the whitelist when using Qemu with Libvirt.
[0] - https://bugzilla.redhat.com/show_bug.cgi?id=855162
Reported-by: Paul Moore <pmoore@redhat.com>...
Adding qemu-seccomp.[ch] (v8)
Signed-off-by: Eduardo Otubo <otubo@linux.vnet.ibm.com>Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>---v1: - I added a syscall struct using priority levels as described in the libseccomp man page. The priority numbers are based to the frequency...