From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: pmoore@redhat.com, coreyb@linux.vnet.ibm.com, wad@chromium.org,
qemu-devel@nongnu.org, Eduardo Otubo <otubo@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH] seccomp: adding a second whitelist
Date: Thu, 29 Aug 2013 10:56:44 +0200 [thread overview]
Message-ID: <521F0CCC.1010301@redhat.com> (raw)
In-Reply-To: <20130829083411.GD23096@stefanha-thinkpad.redhat.com>
Il 29/08/2013 10:34, Stefan Hajnoczi ha scritto:
> On Wed, Aug 28, 2013 at 10:04:32PM -0300, Eduardo Otubo wrote:
>> Now there's a second whitelist, right before the vcpu starts. The second
>> whitelist is the same as the first one, except for exec() and select().
>
> -netdev tap,downscript=/path/to/script requires exec() in the QEMU
> shutdown code path. Will this work with seccomp?
It won't by design (seccomp is supposed to run with file descriptor
passing).
However, removing select() seems a bit risky. We cannot exclude that
external libraries are not using it instead of, say, poll.
BTW, recent QEMU is using ppoll instead of poll; does the whitelist
require an update?
Paolo
next prev parent reply other threads:[~2013-08-29 8:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 1:04 [Qemu-devel] [PATCH] seccomp: adding a second whitelist Eduardo Otubo
2013-08-29 8:34 ` Stefan Hajnoczi
2013-08-29 8:56 ` Paolo Bonzini [this message]
2013-08-30 14:22 ` Eduardo Otubo
2013-08-30 14:21 ` Eduardo Otubo
2013-08-30 15:23 ` Stefan Hajnoczi
2013-08-30 15:42 ` Paul Moore
2013-09-02 9:05 ` Stefan Hajnoczi
2013-09-03 18:02 ` Corey Bryant
2013-09-03 18:08 ` Corey Bryant
2013-09-03 18:21 ` Paul Moore
2013-09-03 18:23 ` Corey Bryant
2013-09-03 20:07 ` Eduardo Otubo
2013-09-03 21:49 ` Paul Moore
2013-09-03 20:05 ` Eduardo Otubo
2013-09-03 21:08 ` Corey Bryant
2013-08-29 12:56 ` Paul Moore
2013-08-30 14:27 ` Eduardo Otubo
2013-08-30 15:32 ` 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=521F0CCC.1010301@redhat.com \
--to=pbonzini@redhat.com \
--cc=coreyb@linux.vnet.ibm.com \
--cc=otubo@linux.vnet.ibm.com \
--cc=pmoore@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=wad@chromium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.