From: Corey Bryant <coreyb@linux.vnet.ibm.com>
To: Paul Moore <pmoore@redhat.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org,
Eduardo Otubo <otubo@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCHv2 1/4] Adding new syscalls (bugzilla 855162)
Date: Fri, 02 Nov 2012 10:49:56 -0400 [thread overview]
Message-ID: <5093DD94.1020002@linux.vnet.ibm.com> (raw)
In-Reply-To: <2826252.GgZdGKF9jS@sifl>
On 11/02/2012 10:46 AM, Paul Moore wrote:
> On Friday, November 02, 2012 10:43:41 AM Corey Bryant wrote:
>> On 11/02/2012 10:38 AM, Paul Moore wrote:
>>> On Friday, November 02, 2012 10:10:02 AM Paul Moore wrote:
>>>> On Friday, November 02, 2012 09:48:55 AM Corey Bryant wrote:
>>>>> On 11/01/2012 05:43 PM, Paul Moore wrote:
>>>>>> On Tuesday, October 23, 2012 03:55:29 AM Eduardo Otubo wrote:
>>>>>>> According to the bug 855162[0] - there's the need of adding new
>>>>>>> syscalls
>>>>>>> to the whitelist whenn using Qemu with Libvirt.
>>>>>>>
>>>>>>> [0] - https://bugzilla.redhat.com/show_bug.cgi?id=855162
>>>>>>>
>>>>>>> v2: Adding new syscalls to the list: readlink, rt_sigpending, and
>>>>>>>
>>>>>>> rt_sigtimedwait
>>>>>>>
>>>>>>> Reported-by: Paul Moore <pmoore@redhat.com>
>>>>>>> Signed-off-by: Eduardo Otubo <otubo@linux.vnet.ibm.com>
>>>>>>> ---
>>>>>>>
>>>>>>> qemu-seccomp.c | 13 ++++++++++++-
>>>>>>> 1 file changed, 12 insertions(+), 1 deletion(-)
>>>>>>
>>>>>> I had an opportunity to test this patchset on a F17 machine using QEMU
>>>>>> 1.2
>>>>>> and unfortunately it still fails. I'm using a relatively basic guest
>>>>>> configuration running F16, the details are documented in the RH BZ that
>>>>>> Eduardo mentioned in the patch description.
>>>>>
>>>>> Paul, Here's the latest diff for the whitelist. We're looking to get
>>>>> the patches out in the next few days after a bit more testing.
>>>>
>>>> Okay, thanks for the updated list ... I'm rebuilding QEMU right now and
>>>> I'll report back with the results later today.
>>>
>>> Sadly, no luck, it still fails.
>>
>> Hmm, let me send you the current patch set off-line, which includes
>> debug support to write the failing syscall out. If you don't mind could
>> you try it out?
>
> Sure, no problem.
>
> On a related note, I think it would be a *really* good idea to also submit the
> debug code upstream, just in a disabled state by default. You could either
> bracket it with #ifdefs or get fancy and allow it at runtime with '-sandbox
> debug' or something similar.
>
I agree. That's the plan with the v3 patch series. We'll get them out
in the next few days.
--
Regards,
Corey Bryant
prev parent reply other threads:[~2012-11-02 14:50 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-23 5:55 [Qemu-devel] [PATCHv2 1/4] Adding new syscalls (bugzilla 855162) Eduardo Otubo
2012-10-23 5:55 ` [Qemu-devel] [PATCHv2 2/4] Setting "-sandbox on" as deafult Eduardo Otubo
2012-10-23 5:55 ` [Qemu-devel] [PATCHv2 3/4] Support for "double whitelist" filters Eduardo Otubo
2012-10-23 15:10 ` Corey Bryant
2012-10-24 20:06 ` Eduardo Otubo
2012-10-25 20:16 ` Eduardo Otubo
2012-11-02 21:29 ` Paul Moore
2012-11-02 22:00 ` Corey Bryant
2012-11-02 22:14 ` Paul Moore
2012-11-05 14:39 ` Corey Bryant
2012-11-05 21:58 ` Paul Moore
2012-11-05 22:26 ` Corey Bryant
2012-11-02 22:01 ` Anthony Liguori
2012-10-23 5:55 ` [Qemu-devel] [PATCHv2 4/4] Warning messages on net devices hotplug Eduardo Otubo
2012-10-23 15:59 ` Corey Bryant
2012-10-23 16:39 ` Eric Blake
2012-11-01 21:43 ` [Qemu-devel] [PATCHv2 1/4] Adding new syscalls (bugzilla 855162) Paul Moore
2012-11-02 2:29 ` Eduardo Otubo
2012-11-02 14:10 ` Paul Moore
2012-11-02 13:48 ` Corey Bryant
2012-11-02 14:10 ` Paul Moore
2012-11-02 14:38 ` Paul Moore
2012-11-02 14:43 ` Corey Bryant
2012-11-02 14:46 ` Paul Moore
2012-11-02 14:49 ` Corey Bryant [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=5093DD94.1020002@linux.vnet.ibm.com \
--to=coreyb@linux.vnet.ibm.com \
--cc=aliguori@us.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 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).