From: Eduardo Otubo <otubo@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: pmoore@redhat.com, debfx@fobos.de
Subject: [Qemu-devel] [PULL 02/02] seccomp: add shmctl(), mlock(), and munlock() to the syscall whitelist
Date: Thu, 13 Mar 2014 10:42:44 -0300 [thread overview]
Message-ID: <1394718164-7883-3-git-send-email-otubo@linux.vnet.ibm.com> (raw)
In-Reply-To: <1394718164-7883-1-git-send-email-otubo@linux.vnet.ibm.com>
From: Paul Moore <pmoore@redhat.com>
Additional testing reveals that PulseAudio requires shmctl() and the
mlock()/munlock() syscalls on some systems/configurations. As before,
on systems that do require these syscalls, the problem can be seen with
the following command line:
# qemu -monitor stdio -sandbox on \
-device intel-hda -device hda-duplex
Signed-off-by: Paul Moore <pmoore@redhat.com>
Acked-by: Eduardo Otubo <otubo@linux.vnet.ibm.com>
---
qemu-seccomp.c | 5 ++++-
1 files changed, 4 insertions(+), 1 deletions(-)
diff --git a/qemu-seccomp.c b/qemu-seccomp.c
index 46554bd..ea8094d 100644
--- a/qemu-seccomp.c
+++ b/qemu-seccomp.c
@@ -227,7 +227,10 @@ static const struct QemuSeccompSyscall seccomp_whitelist[] = {
{ SCMP_SYS(shmget), 240 },
{ SCMP_SYS(shmat), 240 },
{ SCMP_SYS(shmdt), 240 },
- { SCMP_SYS(timerfd_create), 240 }
+ { SCMP_SYS(timerfd_create), 240 },
+ { SCMP_SYS(shmctl), 240 },
+ { SCMP_SYS(mlock), 240 },
+ { SCMP_SYS(munlock), 240 }
};
int seccomp_start(void)
--
1.7.1
next prev parent reply other threads:[~2014-03-13 13:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-13 13:42 [Qemu-devel] [PULL 00/02] seccomp: adding new syscalls to the whitelist Eduardo Otubo
2014-03-13 13:42 ` [Qemu-devel] [PULL 01/02] seccomp: add timerfd_create and timerfd_settime " Eduardo Otubo
2014-03-13 13:42 ` Eduardo Otubo [this message]
2014-03-24 18:13 ` [Qemu-devel] [PULL 00/02] seccomp: adding new syscalls " Paul Moore
2014-04-01 13:06 ` Eduardo Otubo
2014-04-02 15:53 ` Paolo Bonzini
2014-04-03 11:14 ` Peter Maydell
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=1394718164-7883-3-git-send-email-otubo@linux.vnet.ibm.com \
--to=otubo@linux.vnet.ibm.com \
--cc=debfx@fobos.de \
--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).