From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:47594) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Td2Af-0007pL-Bg for qemu-devel@nongnu.org; Mon, 26 Nov 2012 12:08:43 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Td2Ab-00051E-8i for qemu-devel@nongnu.org; Mon, 26 Nov 2012 12:08:37 -0500 Received: from mx1.redhat.com ([209.132.183.28]:57530) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Td2Ab-000515-13 for qemu-devel@nongnu.org; Mon, 26 Nov 2012 12:08:33 -0500 From: Paul Moore Date: Mon, 26 Nov 2012 12:08:28 -0500 Message-ID: <2283866.KgMUQUY9RY@sifl> In-Reply-To: <50B39BA2.8070503@linux.vnet.ibm.com> References: <1352749698-1219-1-git-send-email-otubo@linux.vnet.ibm.com> <3108382.kUZmsgcyl9@sifl> <50B39BA2.8070503@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [Qemu-devel] [PATCHv3 1/5] seccomp: adding new syscalls (bugzilla 855162) List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Corey Bryant Cc: qemu-devel@nongnu.org, Eduardo Otubo On Monday, November 26, 2012 11:41:06 AM Corey Bryant wrote: > On 11/21/2012 10:24 AM, Paul Moore wrote: > > On Wednesday, November 21, 2012 11:20:44 AM Eduardo Otubo wrote: > >> Hello folks, > >> > >> Does anyone had a chance to take a look at this? We would like to get > >> this into the 1.3 release. > >> > >> Thanks again :) > > > > I way a bit delayed due to travel, but I started playing with it a bit > > yesterday afternoon and unfortunately it still doesn't work for me (using > > the same test/reproducer I documented in the RH BZ). I've tried running > > QEMU both via libvirt and the command line (using a libvirt derived > > command line). > > > > I'm applying the patches to the F17 QEMU 1.2 package; there is some minor > > fixup needed in the configure script but nothing major. > > > > What is further frustrating is that the debug code (patch 5/5) doesn't > > seem to output the problematic syscall. I wanted to investigate this a > > bit more before responding, but with the holiday approaching > > (Thanksgiving in the US), I'm not sure how much progress I'll be able to > > make for the remainder of this week. Sorry about that. > > > > If you have any further questions about how, or what, I'm testing, just > > ask. > > Paul, Is your host 32 or 64-bit? 64-bit -- paul moore security and virtualization @ redhat