qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eduardo Otubo <otubo@linux.vnet.ibm.com>
To: Paul Moore <pmoore@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	coreyb@linux.vnet.ibm.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] seccomp: adding times() to the whitelist
Date: Mon, 09 Sep 2013 10:20:10 -0300	[thread overview]
Message-ID: <522DCB0A.30406@linux.vnet.ibm.com> (raw)
In-Reply-To: <11305371.SUiNjF4f3Q@sifl>



On 09/09/2013 09:36 AM, Paul Moore wrote:
> On Monday, September 09, 2013 12:38:12 PM Paolo Bonzini wrote:
>> Il 06/09/2013 20:41, Eduardo Otubo ha scritto:
>>> Hello,
>>>
>>>      Any chance to get this patch applied?
>>>
>>> Thanks!
>>
>> Paul, perhaps you can add yourself to MAINTAINERS and send a pull request?
>>
>> Paolo
>
> Out of respect for the work that Eduardo has done, and is continuing to do,
> with the QEMU seccomp filtering, I think Eduardo should be the one to take on
> this role.  If Eduardo declines I'll do ahead and submit a patch adding myself
> to the MAINTAINERS file.

If this is ok for everyone, I would be really glad to take this role to 
myself. Paul, thanks for this vote of confidence. Paolo, should I send a 
patch for MAINTAINERS right away?

Regards,

>
>>> On 09/04/2013 11:11 AM, Paul Moore wrote:
>>>> On Wednesday, September 04, 2013 09:25:08 AM Eduardo Otubo wrote:
>>>>> This was causing Qemu process to hang when using -sandbox on.
>>>>>
>>>>> Related RHBZ: https://bugzilla.redhat.com/show_bug.cgi?id=1004175
>>>>>
>>>>> Signed-off-by: Eduardo Otubo <otubo@linux.vnet.ibm.com>
>>>>
>>>> Works for me.
>>>>
>>>> Tested-by: Paul Moore <pmoore@redhat.com>
>>>>
>>>>> ---
>>>>>
>>>>>    qemu-seccomp.c |    1 +
>>>>>    1 files changed, 1 insertions(+), 0 deletions(-)
>>>>>
>>>>> diff --git a/qemu-seccomp.c b/qemu-seccomp.c
>>>>> index 37d38f8..69cee44 100644
>>>>> --- a/qemu-seccomp.c
>>>>> +++ b/qemu-seccomp.c
>>>>> @@ -90,6 +90,7 @@ static const struct QemuSeccompSyscall
>>>>> seccomp_whitelist[]
>>>>> = { { SCMP_SYS(getuid), 245 },
>>>>>
>>>>>        { SCMP_SYS(geteuid), 245 },
>>>>>        { SCMP_SYS(timer_create), 245 },
>>>>>
>>>>> +    { SCMP_SYS(times), 245 },
>>>>>
>>>>>        { SCMP_SYS(exit), 245 },
>>>>>        { SCMP_SYS(clock_gettime), 245 },
>>>>>        { SCMP_SYS(time), 245 },
>

-- 
Eduardo Otubo
IBM Linux Technology Center

  reply	other threads:[~2013-09-09 13:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-04 12:25 [Qemu-devel] [PATCH] seccomp: adding times() to the whitelist Eduardo Otubo
2013-09-04 13:10 ` Corey Bryant
2013-09-04 14:11 ` Paul Moore
2013-09-06 18:41   ` Eduardo Otubo
2013-09-09 10:38     ` Paolo Bonzini
2013-09-09 12:36       ` Paul Moore
2013-09-09 13:20         ` Eduardo Otubo [this message]
2013-09-09 13:48           ` [Qemu-devel] seccomp submaintainer? (was Re: [PATCH] seccomp: adding times() to the whitelist) Paolo Bonzini
2013-09-09 14:44             ` Paul Moore
2013-09-09 16:40             ` Anthony Liguori
2013-09-13 14:45   ` [Qemu-devel] [PATCH] seccomp: adding times() to the whitelist Paul Moore
2013-09-23 19:49     ` Eduardo Otubo
2013-09-23 19:54       ` Anthony Liguori
2013-09-23 19:53   ` Paul Moore
2013-09-23 19:56     ` Eduardo Otubo

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=522DCB0A.30406@linux.vnet.ibm.com \
    --to=otubo@linux.vnet.ibm.com \
    --cc=coreyb@linux.vnet.ibm.com \
    --cc=pbonzini@redhat.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).