From: Paul Moore <pmoore@redhat.com>
To: Eduardo Otubo <otubo@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] New syscalls to the seccomp whitelist
Date: Wed, 26 Sep 2012 11:14:29 -0400 [thread overview]
Message-ID: <1559484.FIy5X4RP1O@sifl> (raw)
In-Reply-To: <1348174859-24809-1-git-send-email-otubo@linux.vnet.ibm.com>
On Thursday, September 20, 2012 06:00:59 PM Eduardo Otubo wrote:
> Seccomp syscall whitelist updated after tests running qemu under
> libvirt ...
Hi Eduardo,
I know from our discussions offlist that you have an additional debugging
patch to help identify missing syscalls, perhaps you could also submit that
patch too? I think we would want the debugging patch #ifdef'd out in normal
use, but I think it might help the QEMU developers.
--
paul moore
security and virtualization @ redhat
next prev parent reply other threads:[~2012-09-26 15:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-20 21:00 [Qemu-devel] [PATCH] New syscalls to the seccomp whitelist Eduardo Otubo
2012-09-21 11:21 ` Kevin Wolf
2012-09-21 12:40 ` Eduardo Otubo
2012-09-24 12:36 ` Eduardo Otubo
2012-09-26 16:55 ` Cole Robinson
2012-09-26 20:10 ` Paul Moore
2012-09-26 15:14 ` Paul Moore [this message]
2012-09-26 16:24 ` Eduardo Otubo
2012-09-26 16:42 ` 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=1559484.FIy5X4RP1O@sifl \
--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).