From: Kevin Wolf <kwolf@redhat.com>
To: Corey Bryant <coreyb@linux.vnet.ibm.com>
Cc: libvir-list@redhat.com, aliguori@us.ibm.com, eblake@redhat.com,
qemu-devel@nongnu.org, stefanha@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [RFC PATCH 0/4] block: file descriptor passing using -filefd and getfd_file
Date: Tue, 22 May 2012 16:45:44 +0200 [thread overview]
Message-ID: <4FBBA698.7040805@redhat.com> (raw)
In-Reply-To: <4FBBA2F8.1020300@linux.vnet.ibm.com>
Am 22.05.2012 16:30, schrieb Corey Bryant:
>
>
> On 05/22/2012 04:18 AM, Kevin Wolf wrote:
>> Am 21.05.2012 22:19, schrieb Corey Bryant:
>>> libvirt's sVirt security driver provides SELinux MAC isolation for
>>> Qemu guest processes and their corresponding image files. In other
>>> words, sVirt uses SELinux to prevent a QEMU process from opening
>>> files that do not belong to it.
>>>
>>> sVirt provides this support by labeling guests and resources with
>>> security labels that are stored in file system extended attributes.
>>> Some file systems, such as NFS, do not support the extended
>>> attribute security namespace, and therefore cannot support sVirt
>>> isolation.
>>>
>>> A solution to this problem is to provide fd passing support, where
>>> libvirt opens files and passes file descriptors to QEMU. This,
>>> along with SELinux policy to prevent QEMU from opening files, can
>>> provide image file isolation for NFS files.
>>>
>>> This patch series adds the -filefd command-line option and the
>>> getfd_file monitor command. This will enable libvirt to open a
>>> file and push the corresponding filename and file descriptor to
>>> QEMU. When QEMU needs to "open" a file, it will first check if the
>>> file descriptor was passed by either of these methods before
>>> attempting to actually open the file.
>>
>> I thought we decided to avoid making some file names magic, and instead
>> go for the obvious /dev/fd/42?
>
> I understand that open("/dev/fd/42") would be the same as dup(42), but
> I'm not sure that I'm entirely clear on how this would work. Could you
> give an example?
With your approach you open the file outside qemu, pass the fd to qemu
along with a file name that it's supposed to replace and then you use
that fake file name:
(qemu) getfd_file abc
(qemu) drive_add 0 file=abc,...
Instead you could use the existing getfd command and avoid the translation:
(qemu) getfd
42
(qemu) drive_add 0 file=/dev/fd/42,...
Er, well. Just that getfd doesn't return the assigned fd today, so the
management tool doesn't know it. We would have to add that.
Kevin
next prev parent reply other threads:[~2012-05-22 14:46 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 20:19 [Qemu-devel] [RFC PATCH 0/4] block: file descriptor passing using -filefd and getfd_file Corey Bryant
2012-05-21 20:19 ` [Qemu-devel] [RFC PATCH 1/4] qemu-options: Add -filefd command line option Corey Bryant
2012-05-21 21:40 ` Eric Blake
2012-05-22 13:25 ` Corey Bryant
2012-05-22 13:38 ` Kevin Wolf
2012-05-22 14:26 ` Stefan Hajnoczi
2012-05-22 14:39 ` Kevin Wolf
2012-05-21 20:19 ` [Qemu-devel] [RFC PATCH 2/4] qmp/hmp: Add getfd_file monitor command Corey Bryant
2012-05-21 21:48 ` Eric Blake
2012-05-22 13:37 ` Corey Bryant
2012-05-22 9:18 ` Stefan Hajnoczi
2012-05-22 14:13 ` Corey Bryant
2012-05-22 19:06 ` Luiz Capitulino
2012-05-22 20:02 ` Corey Bryant
2012-05-22 20:26 ` Luiz Capitulino
2012-05-22 22:34 ` Corey Bryant
2012-05-23 13:33 ` Luiz Capitulino
2012-05-23 13:45 ` Corey Bryant
2012-05-21 20:19 ` [Qemu-devel] [RFC PATCH 3/4] block: Enable QEMU to retrieve passed fd before attempting open Corey Bryant
2012-05-21 21:50 ` Eric Blake
2012-05-22 14:06 ` Corey Bryant
2012-05-21 20:19 ` [Qemu-devel] [RFC PATCH 4/4] Example -filefd and getfd_file server Corey Bryant
2012-05-22 8:18 ` [Qemu-devel] [RFC PATCH 0/4] block: file descriptor passing using -filefd and getfd_file Kevin Wolf
2012-05-22 12:02 ` Eric Blake
2012-05-22 12:08 ` Kevin Wolf
2012-05-22 14:30 ` Corey Bryant
2012-05-22 14:45 ` Kevin Wolf [this message]
2012-05-22 15:01 ` Eric Blake
2012-05-22 15:24 ` Kevin Wolf
2012-05-22 15:29 ` Corey Bryant
2012-05-22 15:39 ` Kevin Wolf
2012-05-22 16:02 ` Corey Bryant
2012-05-22 16:15 ` Eric Blake
2012-05-22 17:17 ` Corey Bryant
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=4FBBA698.7040805@redhat.com \
--to=kwolf@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=coreyb@linux.vnet.ibm.com \
--cc=eblake@redhat.com \
--cc=libvir-list@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.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).