Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
The "virtlockd" daemon, which is a daemon responsible for holding POSIX file locks for VMs, is being incorrectly run under the "virtlogd" SELinux domain. "virtlogd" is a daemon responsible for managing VM log files. As such these two daemons have different functionality and need different SELinux rules in order to function.
In current RHEL, when using virtlockd, we get AVCs:
type=AVC msg=audit(1587006887.874:515): avc: denied { write } for pid=1515 comm="virtlockd" name="libvirt" dev="dm-0" ino=4428423 scontext=system_u:system_r:virtlogd_t:s0-s0:c0.c1023 tcontext=system_u:object_r:virt_var_lib_t:s0 tclass=dir permissive=0
There *is* alot in common between what virtlockd and virtlogd need todo, so using virtlogd_t policy rules as a design pattern for virtlockd_t rules is reasonable.
The key difference is that virtlockd_t needs access to create/write (empty) files under /var/lib/libvirt/lockd/ (and any dirs), and needs to be able to fnctl(F_SETLK)) on those files. So /var/lib/libvirt/lockd needs to be labelled with a virt_var_lockd_t type.
virtlockd_t also needs to be able to to call fcntl(F_SETLK) on any block devices under /dev. Possibly this particular rule should be toggled by a policy boolean "virt_lockd_use_devs"
Version-Release number of selected component (if applicable):
selinux-policy-3.14.3-41.el8_2.1.noarch
How reproducible:
See original libvirt bug https://bugzilla.redhat.com/show_bug.cgi?id=1824375
Comment 12Diego Santa Cruz
2020-08-06 14:35:51 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (selinux-policy bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2020:4528
Description of problem: The "virtlockd" daemon, which is a daemon responsible for holding POSIX file locks for VMs, is being incorrectly run under the "virtlogd" SELinux domain. "virtlogd" is a daemon responsible for managing VM log files. As such these two daemons have different functionality and need different SELinux rules in order to function. In current RHEL, when using virtlockd, we get AVCs: type=AVC msg=audit(1587006887.874:515): avc: denied { write } for pid=1515 comm="virtlockd" name="libvirt" dev="dm-0" ino=4428423 scontext=system_u:system_r:virtlogd_t:s0-s0:c0.c1023 tcontext=system_u:object_r:virt_var_lib_t:s0 tclass=dir permissive=0 There *is* alot in common between what virtlockd and virtlogd need todo, so using virtlogd_t policy rules as a design pattern for virtlockd_t rules is reasonable. The key difference is that virtlockd_t needs access to create/write (empty) files under /var/lib/libvirt/lockd/ (and any dirs), and needs to be able to fnctl(F_SETLK)) on those files. So /var/lib/libvirt/lockd needs to be labelled with a virt_var_lockd_t type. virtlockd_t also needs to be able to to call fcntl(F_SETLK) on any block devices under /dev. Possibly this particular rule should be toggled by a policy boolean "virt_lockd_use_devs" Version-Release number of selected component (if applicable): selinux-policy-3.14.3-41.el8_2.1.noarch How reproducible: See original libvirt bug https://bugzilla.redhat.com/show_bug.cgi?id=1824375