Bug 208974

Summary: gfs needs to be added as selinux capable filesystem
Product: Red Hat Enterprise Linux 5 Reporter: Ryan O'Hara <rohara>
Component: selinux-policyAssignee: Daniel Walsh <dwalsh>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 5.0CC: rkenna, rohara
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: beta2 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-12-23 01:00:00 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:
Attachments:
Description Flags
Add gfs to selinux policy none

Description Ryan O'Hara 2006-10-02 20:06:22 UTC
gfs is missing from the SELinux policy (filesystem.te). If I recall, both gfs
and gfs2 were once both identified as filesystems that support SELinux. This is
correct. Looks like only gfs2 is currently defined. Need this added to file
filesystem.te:

fs_use_xattr gfs gen_context(system_u:object_r:fs_t,s0);

Comment 1 Ryan O'Hara 2006-10-02 20:31:30 UTC
Created attachment 137599 [details]
Add gfs to selinux policy

Comment 2 Daniel Walsh 2006-10-05 19:43:29 UTC
Ryan can you remove the private checkbox so I can show this bugzilla to upstream
policy maintainance.



Comment 3 Daniel Walsh 2006-10-18 21:14:23 UTC
Fixed in selinux-policy-2.3.19-3

Comment 4 RHEL Program Management 2006-10-19 01:33:16 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux release.  Product Management has requested further review
of this request by Red Hat Engineering.  This request is not yet committed for
inclusion in release.

Comment 6 RHEL Program Management 2006-12-23 01:00:00 UTC
A package has been built which should help the problem described in 
this bug report. This report is therefore being closed with a resolution 
of CURRENTRELEASE. You may reopen this bug report if the solution does 
not work for you.