Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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.

Bug 667177

Summary: cachefilesd fails to start with SELinux disabled on default config file
Product: Red Hat Enterprise Linux 6 Reporter: Colin.Simpson
Component: kernelAssignee: David Howells <dhowells>
Status: CLOSED ERRATA QA Contact: Petr Beňas <pbenas>
Severity: medium Docs Contact:
Priority: low    
Version: 6.0CC: dhowells, kzhang, lfarkas, pbenas, pstehlik, rwheeler
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: kernel-2.6.32-176.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-06 12:36:35 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
Translate a secctx to 0 if SELinux is disabled none

Description Colin.Simpson 2011-01-04 18:30:02 UTC
Description of problem:

If you attempt to start cachefilesd with SELinux in disabled mode and the default config file it fails with:


Jan  4 18:05:56 rhel6ws cachefilesd[4031]: CacheFiles bind failed: errno 95 (Operation not supported)
Jan  4 18:05:56 rhel6ws kernel: CacheFiles: Security denies permission to nominate security context: error -95
Jan  4 18:16:22 rhel6ws cachefilesd[4179]: About to bind cache
Jan  4 18:16:22 rhel6ws cachefilesd[4179]: CacheFiles bind failed: errno 95 (Operation not supported)
Jan  4 18:16:22 rhel6ws kernel: CacheFiles: Security denies permission to nominate security context: error -95
Jan  4 18:18:33 rhel6ws cachefilesd[4232]: About to bind cache
Jan  4 18:18:33 rhel6ws cachefilesd[4232]: CacheFiles bind failed: errno 95 (Operation not supported)
Jan  4 18:18:33 rhel6ws kernel: CacheFiles: Security denies permission to nominate security context: error -95

# sestatus 
SELinux status:                 disabled

Version-Release number of selected component (if applicable):

cachefilesd-0.10.1-2.el6.x86_64

How reproducible:
Every time

Steps to Reproduce:
1. /etc/init.d/cachefilesd restart
2. tail /var/log/messages
  

Additional info:

Commenting the SELinux line in cachefilesd.conf allows it to start i.e

# Assuming you're using SELinux with the default security policy included in
# this package
#secctx system_u:system_r:cachefiles_kernel_t:s0

Should it not ignore this line if SELinux is disabled?

Comment 2 RHEL Program Management 2011-01-07 15:57:26 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.

Comment 4 Levente Farkas 2011-05-04 06:14:15 UTC
would be nice to fix....

Comment 5 David Howells 2011-07-08 23:16:15 UTC
This is fixed upstream by this patch:

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=2606fd1fa5710205b23ee859563502aa18362447

which, amongst other things, makes cap_secctx_to_secid() return 0 and a security ID of 0 - instead of -EOPNOTSUPP.

Comment 6 David Howells 2011-07-15 14:38:50 UTC
Created attachment 513394 [details]
Translate a secctx to 0 if SELinux is disabled

The patch causes a security context to be translated to a security ID of 0 if SELinux is disabled rather than returning an error.  This permits cachefilesd to start if SELinux is disabled.

Comment 7 RHEL Program Management 2011-07-28 20:10:10 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 Aristeu Rozanski 2011-08-02 13:57:32 UTC
Patch(es) available on kernel-2.6.32-176.el6

Comment 15 Petr Beňas 2011-08-15 07:27:46 UTC
Reproduced in 2.6.32-175.el6.x86_64 and verified in 2.6.32-176.el6.x86_64.

Comment 16 errata-xmlrpc 2011-12-06 12:36:35 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.

http://rhn.redhat.com/errata/RHSA-2011-1530.html