Bug 1210237

Summary: /dev/vhci and /dev/memory_bandwidth do not have specific SELinux labels
Product: Red Hat Enterprise Linux 7 Reporter: Milos Malik <mmalik>
Component: selinux-policyAssignee: Simon Sekidde <ssekidde>
Status: CLOSED ERRATA QA Contact: Milos Malik <mmalik>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.1CC: lvrabec, mgrepl, mmalik, plautrba, pvrabec, ssekidde
Target Milestone: rc   
Target Release: ---   
Hardware: aarch64   
OS: Linux   
Whiteboard:
Fixed In Version: selinux-policy-3.13.1-40.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-19 10:31:26 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Milos Malik 2015-04-09 09:08:55 UTC 
Description of problem:
 * one of our automated TCs found these devices on aarch64 machine

Version-Release number of selected component (if applicable):
selinux-policy-targeted-3.13.1-23.aa7a.noarch
selinux-policy-devel-3.13.1-23.aa7a.noarch
selinux-policy-3.13.1-23.aa7a.noarch

How reproducible:
always

Steps to Reproduce:
1. get an aarch64 machine with RHEL-7.1
2. check the SELinux context of /dev/vhci
3. check the SELinux context of /dev/memory_bandwidth

Actual results:
# matchpathcon /dev/vhci
/dev/vhci	system_u:object_r:device_t:s0
# matchpathcon /dev/memory_bandwidth 
/dev/memory_bandwidth	system_u:object_r:device_t:s0
# 

Expected results:
 * these devices have specific SELinux labels

Additional information:
 * /dev/vhci seems to be a USB Virtual Host Controller Interface
 * /dev/memory_bandwidth is related to Linux PM QoS framework
Comment 4 Lukas Vrabec 2015-08-10 14:54:12 UTC 
commit afc5fc6c51d4cae64c4153d43007c854ffe0651a
Author: Lukas Vrabec <lvrabec>
Date:   Mon Aug 10 16:52:19 2015 +0200

     Add labels for /dev/memory_bandwith and /dev/vhci. Thanks ssekidde
    Resolves:#1210237
Comment 8 errata-xmlrpc 2015-11-19 10:31:26 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://rhn.redhat.com/errata/RHBA-2015-2300.html