From: Paul Moore <pmoore@redhat.com>
To: qemu-devel@nongnu.org, otubo@linux.vnet.ibm.com
Subject: [Qemu-devel] [PATCH] seccomp: add getrusage() to the syscall whitelist for Open vSwitch
Date: Thu, 06 Mar 2014 09:50:17 -0500 [thread overview]
Message-ID: <20140306145017.1761.50037.stgit@localhost> (raw)
When QEMU is used with Open vSwitch it is common to create netdev
script and downscript scripts that use the ovs-vsctl command to manage
the underlying network devices. Unfortunately, ovs-vsctl calls the
getrusage() syscall which is not currently present in the QEMU/seccomp
whistelist.
Signed-off-by: Paul Moore <pmoore@redhat.com>
---
qemu-seccomp.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/qemu-seccomp.c b/qemu-seccomp.c
index caa926e..86210a4 100644
--- a/qemu-seccomp.c
+++ b/qemu-seccomp.c
@@ -225,7 +225,8 @@ static const struct QemuSeccompSyscall seccomp_whitelist[] = {
{ SCMP_SYS(fchmod), 240 },
{ SCMP_SYS(shmget), 240 },
{ SCMP_SYS(shmat), 240 },
- { SCMP_SYS(shmdt), 240 }
+ { SCMP_SYS(shmdt), 240 },
+ { SCMP_SYS(getrusage), 240 }
};
int seccomp_start(void)
next reply other threads:[~2014-03-06 15:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-06 14:50 Paul Moore [this message]
2014-03-06 16:10 ` [Qemu-devel] [PATCH] seccomp: add getrusage() to the syscall whitelist for Open vSwitch Paolo Bonzini
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=20140306145017.1761.50037.stgit@localhost \
--to=pmoore@redhat.com \
--cc=otubo@linux.vnet.ibm.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).