From: Russell Coker <russell@coker.com.au>
To: selinux-refpolicy@vger.kernel.org
Subject: virt_use_sysfs
Date: Fri, 17 Jul 2020 22:20:32 +1000 [thread overview]
Message-ID: <2061951.59CCVTTc8E@liv> (raw)
Does it make sense to not have this enabled by default? Getting meminfo from
sysfs seems like a very reasonable and useful thing for a virtualisation
system to do. Not allowing that doesn't seem to give any benefit but does
have potential for serious problems if things even work like that.
#!!!! This avc can be allowed using one of the these booleans:
# virt_use_sysfs, virt_use_usb
allow svirt_t sysfs_t:file read;
root@sevm:~/pol# setsebool ^C
root@sevm:~/pol# grep sysfs_t /var/log/audit/audit.log
type=AVC msg=audit(1594988146.629:317649): avc: denied { read } for
pid=430606 comm="qemu-system-x86" name="meminfo" dev="sysfs" ino=1777
scontext=system_u:system_r:svirt_t:s0:c518,c853
tcontext=system_u:object_r:sysfs_t:s0 tclass=file permissive=0
type=AVC msg=audit(1594988146.701:317650): avc: denied { read } for
pid=430606 comm="qemu-system-x86" name="max_mem_regions" dev="sysfs" ino=28161
scontext=system_u:system_r:svirt_t:s0:c518,c853
tcontext=system_u:object_r:sysfs_t:s0 tclass=file permissive=0
type=AVC msg=audit(1594988146.701:317651): avc: denied { read } for
pid=430606 comm="qemu-system-x86" name="max_mem_regions" dev="sysfs" ino=28161
scontext=system_u:system_r:svirt_t:s0:c518,c853
tcontext=system_u:object_r:sysfs_t:s0 tclass=file permissive=0
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
next reply other threads:[~2020-07-17 12:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 12:20 Russell Coker [this message]
2020-07-18 12:44 ` virt_use_sysfs Chris PeBenito
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=2061951.59CCVTTc8E@liv \
--to=russell@coker.com.au \
--cc=selinux-refpolicy@vger.kernel.org \
/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.