From: Corey Bryant <coreyb@linux.vnet.ibm.com>
To: Paul Moore <pmoore@redhat.com>
Cc: qemu-devel@nongnu.org, Eduardo Otubo <otubo@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCHv3 1/5] seccomp: adding new syscalls (bugzilla 855162)
Date: Mon, 26 Nov 2012 14:59:21 -0500 [thread overview]
Message-ID: <50B3CA19.1050206@linux.vnet.ibm.com> (raw)
In-Reply-To: <2283866.KgMUQUY9RY@sifl>
On 11/26/2012 12:08 PM, Paul Moore wrote:
> 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
>
I'm having trouble recreating this. I'm running a Fedora 17 64-bit host
and a Fedora 17 64-bit guest with domain XML that mirrors yours.
Here's the domain XML I'm using and the resulting QEMU command line:
Domain XML: http://pastebin.com/DWa4RQ1Y
Command line: http://pastebin.com/2QTWsUhP
I'm running with QEMU commit 8db972cfa469b4e4afd9c65e54e796b83b5ce3a2
which is 1.2.0 with: (a) just the first patch applied, as well as with
(b) all of this patch series applied.
Any thoughts on what could be different?
--
Regards,
Corey Bryant
next prev parent reply other threads:[~2012-11-26 19:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-12 19:48 [Qemu-devel] [PATCHv3 1/5] seccomp: adding new syscalls (bugzilla 855162) Eduardo Otubo
2012-11-12 19:48 ` [Qemu-devel] [PATCHv3 2/5] seccomp: setting "-sandbox on" as deafult Eduardo Otubo
2012-11-21 15:20 ` Andreas Färber
2012-11-27 19:01 ` Anthony Liguori
2012-11-27 19:07 ` Corey Bryant
2012-11-12 19:48 ` [Qemu-devel] [PATCHv3 3/5] net: Disallow device hotplug that causes execve() Eduardo Otubo
2012-11-12 19:48 ` [Qemu-devel] [PATCHv3 4/5] seccomp: double whitelist support Eduardo Otubo
2012-11-12 19:48 ` [Qemu-devel] [PATCHv3 5/5] seccomp: adding debug mode Eduardo Otubo
2012-11-21 13:20 ` [Qemu-devel] [PATCHv3 1/5] seccomp: adding new syscalls (bugzilla 855162) Eduardo Otubo
2012-11-21 15:24 ` Paul Moore
2012-11-26 16:41 ` Corey Bryant
2012-11-26 17:08 ` Paul Moore
2012-11-26 19:59 ` Corey Bryant [this message]
2012-11-26 20:41 ` Paul Moore
2012-11-26 21:48 ` Paul Moore
2012-11-27 16:11 ` Corey Bryant
2012-11-27 16:15 ` Paul Moore
2012-11-21 15:30 ` Andreas Färber
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=50B3CA19.1050206@linux.vnet.ibm.com \
--to=coreyb@linux.vnet.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 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.