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
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
>> ---
>> qemu
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
> ---
> qemu-seccomp.c |5 -
> 1 file changed, 4 inse
Applied. Thanks.
Regards,
Anthony Liguori
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
---
qemu-seccomp.c |5 -
1 file changed, 4 insertions(+), 1 deletion(-)
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
---
qemu-seccomp.c |5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/qemu-seccomp.c b/qemu-seccomp.c
in
