From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:41573) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Yb9My-0001SQ-J5 for qemu-devel@nongnu.org; Thu, 26 Mar 2015 11:06:58 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Yb9Mv-000651-70 for qemu-devel@nongnu.org; Thu, 26 Mar 2015 11:06:52 -0400 Received: from mail-wg0-f53.google.com ([74.125.82.53]:34755) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Yb9Mv-00064J-17 for qemu-devel@nongnu.org; Thu, 26 Mar 2015 11:06:49 -0400 Received: by wgs2 with SMTP id 2so67808888wgs.1 for ; Thu, 26 Mar 2015 08:06:48 -0700 (PDT) Date: Thu, 26 Mar 2015 16:06:45 +0100 From: Eduardo Otubo Message-ID: <20150326150645.GC24566@vader> References: <1427279169-3213-1-git-send-email-eduardo.otubo@profitbricks.com> <1427279169-3213-2-git-send-email-eduardo.otubo@profitbricks.com> <87oanfx4i8.fsf@neno.neno> <20150326143705.GA24566@vader> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="IpbVkmxF4tDyP/Kb" Content-Disposition: inline In-Reply-To: Subject: Re: [Qemu-devel] [PULL for v2.3 01/01] seccomp: update libseccomp version and remove arch restriction List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: Paul Moore , QEMU Developers , Juan Quintela --IpbVkmxF4tDyP/Kb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Mar 26, 2015 at 02=3D44=3D14PM +0000, Peter Maydell wrote: > On 26 March 2015 at 14:37, Eduardo Otubo = wrote: > > I completely understand your concern. Perhaps a ping on libseccomp > > Fedora package maintainer would be a better way to tackle this issue > > instead of reverting this commit. Libseccomp 2.2.0 is released since Feb > > 12th and I actually gave it a little time frame for other distros to > > update their packages so we don't run into issues like this. >=20 > Well, we shouldn't really be mandating latest-and-greatest versions > of our upstream dependencies unless the maintainer of those dependencies > feels the earlier versions are so badly broken that it would be better > to refuse to use them at all. >=20 > > It's important to remember that this patch is also the proper fix for > > this bug: https://bugs.launchpad.net/qemu/+bug/1363641 >=20 > If that only applies to certain architectures we can make the > dependency version vary depending on which arch we're building > for, I suppose. >=20 This sounds more like a reasonable approach that could solve the above mentioned problem and also making virt-test to be able to keep using this feature as well -- which is also very important in order to get more important system calls for the whitelist. I'll roll out a new patch for that. Thanks for the idea, Paul. Sorry for the trouble on your side, Juan. Regards, --=20 Eduardo Otubo ProfitBricks GmbH --IpbVkmxF4tDyP/Kb Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJVFCCFAAoJEP0M/1sS+L0vCawIAJCdL7F506E8/A57kw42G5w9 4MqzZCy/WVeU5FP+8Z10Be6KhbJLesVRBb19PQf2BoKEoLLE3QSbBXZrUk1YkY9Q 02g4mNijjXrWSrCK6U+1T0E2yDNtKGX6H1jIpOdH64bMsJSJ1g3gGiH7lu9+zea2 jtqKfaLKmE9cMte5rWejjukkLQvQBQdgJbrLsCMQjAymiJuRdomlc1IrsHQPxAb0 dJxQ9HINzOAnynezgMMeFny08CKXojhpiE5GU6Z8j6Fnxt7zugkydhnvDUfn9EnN 20O4qU+2QhSGG9wlsW6YIiu9oHnlrp29nRIWYSXyJTQ0ME+JszuCVPcdceu0U3I= =XUA5 -----END PGP SIGNATURE----- --IpbVkmxF4tDyP/Kb--