Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 442899

Summary: matchpathcon_filespec_add: conflicting specifications for /sbin/mkfs.gfs and /sbin/gfs_mkfs
Product: Red Hat Enterprise Linux 5 Reporter: Milan Zázrivec <mzazrivec>
Component: gfs-utilsAssignee: Robert Peterson <rpeterso>
Status: CLOSED CURRENTRELEASE QA Contact: GFS Bugs <gfs-bugs>
Severity: low Docs Contact:
Priority: low    
Version: 5.2CC: dwalsh, edamato
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: u2 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-07-15 15:31:28 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
setfiles output none

Description Milan Zázrivec 2008-04-17 14:22:24 UTC 
Description of problem:
Running setfiles command produces several error messagess complaining about
conflicting specifications for several files in /sbin

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

How reproducible:
Always

Steps to Reproduce:
1. # setfiles -vqn /etc/selinux/targeted/contexts/files/file_contexts /sbin/
  
Actual results:
Attachment
Comment 1 Milan Zázrivec 2008-04-17 14:22:24 UTC 
Created attachment 302751 [details]
setfiles output
Comment 2 Daniel Walsh 2008-04-17 15:04:06 UTC 
The problem here is there are multiple paths to the same file,  from an SELinux
point of view, it would be much easier if these were all symbolic links versus
hard links.
Comment 3 Robert Peterson 2008-04-17 16:44:49 UTC 
The e2fs utils use hard links as well.  Are you saying this is wrong?

[root@bigi /home/bob]# stat /sbin/e2fsck | grep Inode
Device: fd00h/64768d    Inode: 196694      Links: 3
[root@bigi /home/bob]# stat /sbin/fsck.ext2 | grep Inode
Device: fd00h/64768d    Inode: 196694      Links: 3
[root@bigi /home/bob]# stat /sbin/fsck.ext3 | grep Inode
Device: fd00h/64768d    Inode: 196694      Links: 3
Comment 4 Robert Peterson 2008-04-17 16:48:22 UTC 
Clarification: The gfs-utils and gfs2-utils were originally symlinks
and I was asked specifically to change them to hard links to match ext3
in bug #286211.  I personally don't care; I just need to know which is
proper.  Since gfs and gfs2 are following in the footsteps of ext3,
if it's valid for ext, shouldn't it be valid for gfs as well?
Comment 7 RHEL Program Management 2008-06-04 22:45:01 UTC 
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
release.
Comment 9 Daniel Walsh 2008-07-15 15:31:28 UTC 
I believe these are fixed in U2.