On Wednesday, May 29, 2013 04:30:01 PM Paul Moore wrote:
In order to enable the asynchronous I/O functionality when using the
seccomp sandbox we need to add the associated syscalls to the
whitelist.
Signed-off-by: Paul Moore pmo...@redhat.com
---
qemu-seccomp.c |5 -
1 file
Am 10.07.2013 16:31, schrieb Paul Moore:
On Wednesday, May 29, 2013 04:30:01 PM Paul Moore wrote:
In order to enable the asynchronous I/O functionality when using the
seccomp sandbox we need to add the associated syscalls to the
whitelist.
Signed-off-by: Paul Moore pmo...@redhat.com
---
On Wednesday, July 10, 2013 10:02:55 PM Andreas Färber wrote:
Am 10.07.2013 16:31, schrieb Paul Moore:
On Wednesday, May 29, 2013 04:30:01 PM Paul Moore wrote:
In order to enable the asynchronous I/O functionality when using the
seccomp sandbox we need to add the associated syscalls to the
Applied. Thanks.
Regards,
Anthony Liguori
In order to enable the asynchronous I/O functionality when using the
seccomp sandbox we need to add the associated syscalls to the
whitelist.
Signed-off-by: Paul Moore pmo...@redhat.com
---
qemu-seccomp.c |5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/qemu-seccomp.c
On 05/29/2013 04:30 PM, Paul Moore wrote:
In order to enable the asynchronous I/O functionality when using the
seccomp sandbox we need to add the associated syscalls to the
whitelist.
Signed-off-by: Paul Moore pmo...@redhat.com
---
qemu-seccomp.c |5 -
1 file changed, 4
