kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: quintela@redhat.com
Cc: KVM devel mailing list <kvm@vger.kernel.org>,
	Developers qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] KVM call agenda for Novemeber 22
Date: Mon, 21 Nov 2011 14:43:45 -0600	[thread overview]
Message-ID: <4ECAB801.5090708@codemonkey.ws> (raw)
In-Reply-To: <87aa7pfosp.fsf@neno.neno>

On 11/21/2011 10:00 AM, Juan Quintela wrote:
>
> Hi
>
> Please send in any agenda items you are interested in covering.

I'm technical on holiday this week so I won't be attending.

But as an FYI, I ran across seccomp-nurse[1] this weekend.  It more or less 
let's you write a python program to implement a userspace syscall whitelist.

I haven't looked at the code close enough yet, but I think the technique it uses 
is to create a companion thread along side the sandbox thread.  This thread only 
runs code in an area mapped read-only and presumably only uses thread local storage.

The companion thread isn't running in the sandbox, but has the same resources as 
the sandbox thread so it can essentially invoke syscalls on behalf of the 
sandbox thread.

It's seriously non-portable.  In fact, it only works on 32-bit x86 Linux right 
now.  But it's worth looking into.

[1] http://chdir.org/~nico/seccomp-nurse/

Regards,

Anthony Liguori

>
> Later, Juan.
>


  reply	other threads:[~2011-11-21 20:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-21 16:00 KVM call agenda for Novemeber 22 Juan Quintela
2011-11-21 20:43 ` Anthony Liguori [this message]
2011-11-22 14:39 ` Juan Quintela
2011-11-22 15:00   ` [Qemu-devel] " Stefan Hajnoczi
2011-11-22 15:12     ` Stefan Hajnoczi
2011-11-23  1:44 ` 王永博
2011-11-23  3:07   ` [Qemu-devel] " Alex Jia
2011-11-23  3:11     ` 王永博

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=4ECAB801.5090708@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    /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).