From: alexander.wetzel@web.de (Alexander Wetzel)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH] proposal for libvirt vfio/vt-d support
Date: Tue, 09 Jun 2015 00:39:00 +0200 [thread overview]
Message-ID: <55761984.6030009@web.de> (raw)
In-Reply-To: <20150608213723.GB6341@x131e>
>> Since it's working now without
>> "allow virtd_t vfio_device_t:chr_file setattr;"
>> I've also dropped that from the patch.
>
> I wonder what that is all about. Back when i was using this functionality this only worked with root UID.
> I wonder if that is still the case. Maybe it now works with unprivilege UID and it may need to set attributes in that scenario.
I may mix it up after all the time since checking the documentation, but for my understanding vfio is the "new" device passthrough,
which no longer needs root privileges. The virtual test instance is running with the user qemu and the /dev/vfio/2 device created
for the passthrough is also owned by qemu:
# ls -lZ /dev/vfio/
total 0
crw-------. 1 qemu qemu system_u:object_r:svirt_image_t:s0:c412,c565 248, 0 Jun 8 15:44 2
crw-rw-rw-. 1 root root system_u:object_r:vfio_device_t:s0 10, 196 Jun 7 22:08 vfio
Nevertheless I do not need setattr any longer, sesearch is not finding any rule for that but it's still working.
next prev parent reply other threads:[~2015-06-08 22:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <55746E03.90502@web.de>
2015-06-07 16:28 ` [refpolicy] [PATCH] proposal for libvirt vfio/vt-d support Alexander Wetzel
2015-06-07 17:02 ` Dominick Grift
2015-06-07 17:12 ` Dominick Grift
2015-06-07 17:26 ` Dominick Grift
2015-06-08 21:11 ` Alexander Wetzel
2015-06-08 21:37 ` Dominick Grift
2015-06-08 22:39 ` Alexander Wetzel [this message]
2015-06-09 13:52 ` Dominick Grift
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=55761984.6030009@web.de \
--to=alexander.wetzel@web.de \
--cc=refpolicy@oss.tresys.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.