From: Corey Bryant <coreyb@linux.vnet.ibm.com>
To: Eduardo Otubo <otubo@linux.vnet.ibm.com>
Cc: pmoore@redhat.com, aliguori@us.ibm.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/4] Setting "-sandbox on" as deafult
Date: Thu, 18 Oct 2012 11:08:34 -0400 [thread overview]
Message-ID: <50801B72.5050809@linux.vnet.ibm.com> (raw)
In-Reply-To: <1350479712-15082-2-git-send-email-otubo@linux.vnet.ibm.com>
I think it's worth nothing that Eduardo is planning to submit a separate
patch providing (commented out?) code that will allow developers to
easily determine the syscalls that need to be added to the whitelist.
That is, if QEMU is being killed by seccomp due to disallowed syscall usage.
--
Regards,
Corey Bryant
next prev parent reply other threads:[~2012-10-18 15:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-17 13:15 [Qemu-devel] [PATCH 1/4] Adding new syscalls (bugzilla 855162) Eduardo Otubo
2012-10-17 13:15 ` [Qemu-devel] [PATCH 2/4] Setting "-sandbox on" as deafult Eduardo Otubo
2012-10-18 15:08 ` Corey Bryant [this message]
2012-10-17 13:15 ` [Qemu-devel] [PATCH 3/4] Support for "double whitelist" filters Eduardo Otubo
2012-10-19 17:04 ` Blue Swirl
2012-10-19 20:08 ` Corey Bryant
2012-10-19 20:36 ` Eric Blake
2012-10-19 20:46 ` Corey Bryant
2012-10-19 20:03 ` Corey Bryant
2012-10-17 13:15 ` [Qemu-devel] [PATCH 4/4] Warning messages on net devices hotplug Eduardo Otubo
2012-10-18 14:59 ` Corey Bryant
2012-10-18 15:15 ` Paolo Bonzini
2012-10-24 14:18 ` Corey Bryant
2012-10-24 14:34 ` Corey Bryant
2012-10-24 15:21 ` Paolo Bonzini
2012-10-24 15:39 ` Corey Bryant
2012-10-24 15:45 ` Paolo Bonzini
2012-10-24 15:56 ` Corey Bryant
2012-10-24 17:30 ` Corey Bryant
2012-10-25 7:40 ` Paolo Bonzini
2012-10-26 14:14 ` Corey Bryant
2012-10-19 19:58 ` [Qemu-devel] [PATCH 1/4] Adding new syscalls (bugzilla 855162) Corey Bryant
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=50801B72.5050809@linux.vnet.ibm.com \
--to=coreyb@linux.vnet.ibm.com \
--cc=aliguori@us.ibm.com \
--cc=otubo@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).