From: Paul Moore <pmoore@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Marcus Meissner <meissner@suse.de>,
Karl-Philipp Richter <krichter722@aol.de>,
Riku Voipio <riku.voipio@iki.fi>,
qemu-devel <qemu-devel@nongnu.org>,
Alexander Graf <agraf@suse.de>, qemu-ppc <qemu-ppc@nongnu.org>,
Eduardo Otubo <eduardo.otubo@profitbricks.com>
Subject: Re: [Qemu-devel] seccomp breakage on arm
Date: Fri, 10 Apr 2015 18:56:44 -0400 [thread overview]
Message-ID: <1595331.sxpEq01QmG@sifl> (raw)
In-Reply-To: <5527EEF8.7020209@suse.de>
On Friday, April 10, 2015 05:40:40 PM Andreas Färber wrote:
> My main concern - that you apparently misunderstood - was whether this
> is a QEMU or a libseccomp issue. If it's on libseccomp's side then it's
> less urgent for QEMU and any new configure checks are just candy IMO.
My opinion is that the 32-bit ARM build issue you described is a libseccomp
bug (see the bug fix I sent a few hours ago); QEMU's usage of libseccomp is
perfectly reasonable. That said, the libseccomp bug clearly affected QEMU in
a bad way. Making matters worse is that the problem wasn't caught until late
in the QEMU release process, nobody likes surprises like this.
We've corrected the issue in libseccomp, and it looks like the QEMU folks are
reverting ARM/seccomp support so I think we've resolved this for the immediate
future. Long term I think the libseccomp project can look at adding some
additional automated tests so these issues will be caught at build/packaging
time, further, I think the QEMU project can restore ARM/seccomp support in the
next release and look at its own testing procedures to understand why this
issue wasn't caught earlier as well.
--
paul moore
security @ redhat
prev parent reply other threads:[~2015-04-10 22:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-09 3:01 [Qemu-devel] seccomp breakage on arm Andreas Färber
2015-04-09 8:21 ` Eduardo Otubo
2015-04-09 9:10 ` Paul Moore
2015-04-09 12:28 ` Andreas Färber
2015-04-09 21:27 ` Paul Moore
2015-04-09 22:32 ` Peter Maydell
2015-04-09 23:46 ` Paul Moore
2015-04-10 12:44 ` Peter Maydell
2015-04-10 15:16 ` Paul Moore
2015-04-10 15:38 ` Peter Maydell
2015-04-10 15:40 ` Andreas Färber
2015-04-10 22:56 ` Paul Moore [this message]
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=1595331.sxpEq01QmG@sifl \
--to=pmoore@redhat.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=eduardo.otubo@profitbricks.com \
--cc=krichter722@aol.de \
--cc=meissner@suse.de \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=riku.voipio@iki.fi \
/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).