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.
Bug 1581225 - allow hypervvssd_t to perform stat() on devices
Summary: allow hypervvssd_t to perform stat() on devices
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: selinux-policy
Version: 7.6
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Lukas Vrabec
QA Contact: Milos Malik
URL:
Whiteboard:
Depends On:
Blocks: 1577692
TreeView+ depends on / blocked
 
Reported: 2018-05-22 11:46 UTC by Vitaly Kuznetsov
Modified: 2018-10-30 10:04 UTC (History)
9 users (show)

Fixed In Version: selinux-policy-3.13.1-197.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-30 10:04:11 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:3111 0 None None None 2018-10-30 10:04:48 UTC

Description Vitaly Kuznetsov 2018-05-22 11:46:24 UTC
There is a bug reported against hyperv-daemons:
https://bugzilla.redhat.com/show_bug.cgi?id=1577692

which may also require us to do z-stream. There is an upstream commit
fixing the issue:

commit ea81fdf0981d9a4a998a015d325bed67624811f7
Author: Alex Ng <alexng.com>
Date:   Sun Aug 6 13:12:52 2017 -0700

    Tools: hv: vss: Skip freezing filesystems backed by loop

(which has its own issues, I'm going to address these upstream).

Anyway, with this commit included hypervvssd tries to do stat() on all block devices in /dev/ and SELinux blocks it:

time->Tue May 22 18:42:07 2018
type=SYSCALL msg=audit(1526985727.990:120): arch=c000003e syscall=4 success=no exit=-13 a0=7fb2ee1ff250 a1=7ffe3c08a7f0 a2=7ffe3c08a7f0 a3=4000 items=0 ppid=1 pid=647 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="hypervvssd" exe="/usr/sbin/hypervvssd" subj=system_u:system_r:hypervvssd_t:s0 key=(null)
type=AVC msg=audit(1526985727.990:120): avc:  denied  { getattr } for  pid=647 comm="hypervvssd" path="/dev/dm-0" dev="devtmpfs" ino=9137 scontext=system_u:system_r:hypervvssd_t:s0 tcontext=system_u:object_r:fixed_disk_device_t:s0 tclass=blk_file

We need to get this fixed at least for 7.6 where the hypervvssd commit in question is already present and prepare for z-stream update in case the request will be granted.

audit2allow produces the following output:
allow hypervvssd_t fixed_disk_device_t:blk_file getattr;

but I'm not sure about fixed_disk_device_t as we probably want all block devices.

Comment 6 errata-xmlrpc 2018-10-30 10:04:11 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, 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-2018:3111


Note You need to log in before you can comment on or make changes to this bug.