From: Eduardo Otubo <otubo@linux.vnet.ibm.com>
To: Paul Moore <pmoore@redhat.com>
Cc: Corey Bryant <coreyb@linux.vnet.ibm.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] seccomp: add some basic shared memory syscalls to the whitelist
Date: Thu, 16 Jan 2014 13:53:51 -0200 [thread overview]
Message-ID: <52D8008F.5070003@linux.vnet.ibm.com> (raw)
In-Reply-To: <20140115193858.10562.38583.stgit@localhost>
On 01/15/2014 05:38 PM, Paul Moore wrote:
> PulseAudio requires the use of shared memory so add shmget(), shmat(),
> and shmdt() to the syscall whitelist.
>
> Reported-by: xuhan@redhat.com
> Signed-off-by: Paul Moore <pmoore@redhat.com>
> ---
> qemu-seccomp.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/qemu-seccomp.c b/qemu-seccomp.c
> index 89f244f..caa926e 100644
> --- a/qemu-seccomp.c
> +++ b/qemu-seccomp.c
> @@ -222,7 +222,10 @@ static const struct QemuSeccompSyscall seccomp_whitelist[] = {
> { SCMP_SYS(io_destroy), 241 },
> { SCMP_SYS(arch_prctl), 240 },
> { SCMP_SYS(mkdir), 240 },
> - { SCMP_SYS(fchmod), 240 }
> + { SCMP_SYS(fchmod), 240 },
> + { SCMP_SYS(shmget), 240 },
> + { SCMP_SYS(shmat), 240 },
> + { SCMP_SYS(shmdt), 240 }
ACK.
--
Eduardo Otubo
IBM Linux Technology Center
next prev parent reply other threads:[~2014-01-16 15:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 19:38 [Qemu-devel] [PATCH 0/2] QEMU/seccomp fixes for PulseAudio Paul Moore
2014-01-15 19:38 ` [Qemu-devel] [PATCH 1/2] seccomp: add mkdir() and fchmod() to the whitelist Paul Moore
2014-01-16 15:53 ` Eduardo Otubo
2014-01-15 19:38 ` [Qemu-devel] [PATCH 2/2] seccomp: add some basic shared memory syscalls " Paul Moore
2014-01-16 15:53 ` Eduardo Otubo [this message]
2014-01-16 15:52 ` [Qemu-devel] [PATCH 0/2] QEMU/seccomp fixes for PulseAudio Eduardo Otubo
2014-01-16 15:57 ` Paul Moore
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=52D8008F.5070003@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 \
/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).