Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 240892

Summary: /dev/twe0 needs a chcon (3w_xxxx)
Product: Red Hat Enterprise Linux 5 Reporter: Joshua Daniel Franklin <joshuadfranklin>
Component: selinux-policyAssignee: Daniel Walsh <dwalsh>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 5.0   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-05-22 18:46:31 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Joshua Daniel Franklin 2007-05-22 17:56:40 UTC
Description of problem:
The devices /dev/twe* (for older 3ware controllers) have the
wrong context. Similar to #232218, but in this case the
driver is 3w_xxxx and the devices are /dev/twe*.

This fixed it temporarily for me:
for i in /dev/twe*; do chcon -t fixed_disk_device_t $i; done

sealert reports this:

Summary
    SELinux is preventing /usr/sbin/smartd (fsdaemon_t) "getattr" access to
    device /dev/twe0.

Detailed Description
    SELinux has denied the /usr/sbin/smartd (fsdaemon_t) "getattr" access to
    device /dev/twe0. /dev/twe0 is mislabeled, this device has the default label
    of the /dev directory, which should not happen.




Version-Release number of selected component (if applicable):
selinux-policy-2.4.6-30.el5

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Daniel Walsh 2007-05-22 18:46:31 UTC
The same fix for 232218 fixes this problem.

*** This bug has been marked as a duplicate of 232218 ***

Comment 2 Joshua Daniel Franklin 2007-07-09 23:47:20 UTC
I'm not sure there is a fix for Bug #232218 yet, unless
you mean the updated SELinux Reference Policy:
http://oss.tresys.com/projects/refpolicy/changeset/2246
I assume you're the "Dan" mentioned in the ChangeLog.

That's only a fix for Fedora 7. Will RHEL 5.1 or another
future update include an updated SELinux Reference Policy?

Comment 3 Daniel Walsh 2007-07-11 18:05:18 UTC
Yes this should be fixed in the u1 policy.  You can grab a prerelease at
http://people.redhat.com/dwalsh/SELinux/RHEL5