From: Eduardo Otubo <otubo@linux.vnet.ibm.com>
To: Paul Moore <pmoore@redhat.com>
Cc: coreyb@linux.vnet.ibm.com, qemu-devel@nongnu.org, qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] seccomp: add additional asynchronous I/O syscalls
Date: Wed, 24 Jul 2013 15:02:23 -0300 [thread overview]
Message-ID: <51F016AF.1060406@linux.vnet.ibm.com> (raw)
In-Reply-To: <25459616.lz6518apqg@sifl>
On 07/23/2013 10:57 AM, Paul Moore wrote:
> On Monday, July 15, 2013 03:32:01 PM Paul Moore wrote:
>> A previous commit, "seccomp: add the asynchronous I/O syscalls to the
>> whitelist", added several asynchronous I/O syscalls but left out the
>> io_submit() and io_cancel() syscalls. This patch corrects this by
>> adding the two missing asynchronous I/O syscalls.
>>
>> Signed-off-by: Paul Moore <pmoore@redhat.com>
>
> A gentle nudge so this fix doesn't get forgotten.
Reviewed and tested.
Reviewed-by: Eduardo Otubo <otubo@linux.vnet.ibm.com>
>
>> ---
>> qemu-seccomp.c | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/qemu-seccomp.c b/qemu-seccomp.c
>> index ca123bf..173d185 100644
>> --- a/qemu-seccomp.c
>> +++ b/qemu-seccomp.c
>> @@ -33,6 +33,7 @@ static const struct QemuSeccompSyscall seccomp_whitelist[]
>> = { { SCMP_SYS(socketcall), 250 },
>> #endif
>> { SCMP_SYS(read), 249 },
>> + { SCMP_SYS(io_submit), 249 },
>> { SCMP_SYS(brk), 248 },
>> { SCMP_SYS(clone), 247 },
>> { SCMP_SYS(mmap), 247 },
>> @@ -231,6 +232,7 @@ static const struct QemuSeccompSyscall
>> seccomp_whitelist[] = { { SCMP_SYS(recvmmsg), 241 },
>> { SCMP_SYS(prlimit64), 241 },
>> { SCMP_SYS(waitid), 241 },
>> + { SCMP_SYS(io_cancel), 241 },
>> { SCMP_SYS(io_setup), 241 },
>> { SCMP_SYS(io_destroy), 241 }
>> };
--
Eduardo Otubo
IBM Linux Technology Center
next prev parent reply other threads:[~2013-07-24 18:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-15 19:32 [Qemu-devel] [PATCH] seccomp: add additional asynchronous I/O syscalls Paul Moore
2013-07-23 13:57 ` Paul Moore
2013-07-24 18:02 ` Eduardo Otubo [this message]
2013-07-29 22:12 ` Paul Moore
2013-08-02 12:35 ` Anthony Liguori
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51F016AF.1060406@linux.vnet.ibm.com \
--to=otubo@linux.vnet.ibm.com \
--cc=coreyb@linux.vnet.ibm.com \
--cc=pmoore@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).