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:
I believe that /dev/bsr4096_* should not be labelled device_t.

Version-Release number of selected component (if applicable):
selinux-policy-targeted-3.7.19-115.el6.noarch
selinux-policy-mls-3.7.19-115.el6.noarch
selinux-policy-3.7.19-115.el6.noarch
udev-147-2.40.el6.ppc64
  
Actual results:
# ls -Z /dev/bsr4096_0
crw-rw----. root root system_u:object_r:device_t:s0    /dev/bsr4096_0
# ls -l /dev/bsr4096_0
crw-rw----. 1 root root 251, 0 Oct 10 00:39 /dev/bsr4096_0
#

Eric, any idea how we should label it?

What kind of device is it?  Google returns nothing.

my best guess is: IBM POWER Barrier Synchronization Register

Milos, Sure but have no idea what the proper label should be.

cpu_device_t may be as close as we have unless we want to add a new device type.

Milos, could you just label it using chcon and leave this label for a while during your testing.

I am fine with cpu_device_t.

Fixed in selinux-policy-3_7_19-117_el6

/dev/bsr.*		-c	gen_context(system_u:object_r:cpu_device_t,s0)

Is in F16/Rawhide.

Fixed in selinux-policy-3.7.19-119.el6

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.

http://rhn.redhat.com/errata/RHBA-2011-1511.html