From: Avi Kivity <avi@redhat.com>
To: Alex Bradbury <asb@asbradbury.org>
Cc: KVM list <kvm@vger.kernel.org>,
qemu-devel <qemu-devel@nongnu.org>,
"Richard W.M. Jones" <rjones@redhat.com>
Subject: Re: [Qemu-devel] Idea: fuse-kvm filesystem
Date: Thu, 10 May 2012 15:56:06 +0300 [thread overview]
Message-ID: <4FABBAE6.2020300@redhat.com> (raw)
In-Reply-To: <CA+wH294hVoiGo5JQMcfMPD1Rhsj6UwPX16mxCWTUouVykOdpLw@mail.gmail.com>
On 05/10/2012 03:37 PM, Alex Bradbury wrote:
> On 10 May 2012 13:29, Avi Kivity <avi@redhat.com> wrote:
> > Currently when you mount a filesystem, you face two issues:
> > - you have to be root
> > - if the media is untrusted, it can exploit your kernel
> >
> > With kvm and fuse, we can have a virtualized kernel mount the
> > filesystem, and re-export to the host, which mounts it using a fuse
> > interface. This solves both problems, at the expense of speed and
> > simplicity. In theory this can be used for mounting untrusted USB
> > sticks (perhaps only for the less well tested filesystems).
>
> Is this not one of the many features of guestfs? At least, I'm not
> sure I understand from your description how it's different.
>
> http://libguestfs.org/guestmount.1.html
It is a subset of guestmount, libguestfs rocks.
--
error compiling committee.c: too many arguments to function
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Alex Bradbury <asb@asbradbury.org>
Cc: qemu-devel <qemu-devel@nongnu.org>,
KVM list <kvm@vger.kernel.org>,
"Richard W.M. Jones" <rjones@redhat.com>
Subject: Re: [Qemu-devel] Idea: fuse-kvm filesystem
Date: Thu, 10 May 2012 15:56:06 +0300 [thread overview]
Message-ID: <4FABBAE6.2020300@redhat.com> (raw)
In-Reply-To: <CA+wH294hVoiGo5JQMcfMPD1Rhsj6UwPX16mxCWTUouVykOdpLw@mail.gmail.com>
On 05/10/2012 03:37 PM, Alex Bradbury wrote:
> On 10 May 2012 13:29, Avi Kivity <avi@redhat.com> wrote:
> > Currently when you mount a filesystem, you face two issues:
> > - you have to be root
> > - if the media is untrusted, it can exploit your kernel
> >
> > With kvm and fuse, we can have a virtualized kernel mount the
> > filesystem, and re-export to the host, which mounts it using a fuse
> > interface. This solves both problems, at the expense of speed and
> > simplicity. In theory this can be used for mounting untrusted USB
> > sticks (perhaps only for the less well tested filesystems).
>
> Is this not one of the many features of guestfs? At least, I'm not
> sure I understand from your description how it's different.
>
> http://libguestfs.org/guestmount.1.html
It is a subset of guestmount, libguestfs rocks.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-05-10 12:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-10 12:29 Idea: fuse-kvm filesystem Avi Kivity
2012-05-10 12:29 ` [Qemu-devel] " Avi Kivity
2012-05-10 12:35 ` Richard W.M. Jones
2012-05-10 12:35 ` [Qemu-devel] " Richard W.M. Jones
2012-05-10 12:55 ` Avi Kivity
2012-05-10 12:55 ` [Qemu-devel] " Avi Kivity
2012-05-10 12:37 ` Alex Bradbury
2012-05-10 12:37 ` Alex Bradbury
2012-05-10 12:56 ` Avi Kivity [this message]
2012-05-10 12:56 ` Avi Kivity
2012-05-10 14:09 ` Jan Kiszka
2012-05-10 14:09 ` [Qemu-devel] " Jan Kiszka
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=4FABBAE6.2020300@redhat.com \
--to=avi@redhat.com \
--cc=asb@asbradbury.org \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=rjones@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 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.