From: Avi Kivity <avi@redhat.com>
To: KVM list <kvm@vger.kernel.org>,
qemu-devel <qemu-devel@nongnu.org>,
"Richard W.M. Jones" <rjones@redhat.com>
Subject: [Qemu-devel] Idea: fuse-kvm filesystem
Date: Thu, 10 May 2012 15:29:54 +0300 [thread overview]
Message-ID: <4FABB4C2.3050601@redhat.com> (raw)
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).
--
error compiling committee.c: too many arguments to function
next reply other threads:[~2012-05-10 12:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-10 12:29 Avi Kivity [this message]
2012-05-10 12:35 ` [Qemu-devel] Idea: fuse-kvm filesystem Richard W.M. Jones
2012-05-10 12:55 ` Avi Kivity
2012-05-10 12:37 ` Alex Bradbury
2012-05-10 12:56 ` Avi Kivity
2012-05-10 14:09 ` 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=4FABB4C2.3050601@redhat.com \
--to=avi@redhat.com \
--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 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).