Bug 459390

Summary: "permission ioctl is not defined for class sock_file" when using nscd_socket_use macro
Product: Red Hat Enterprise Linux 5 Reporter: Aleksander Adamowski <bugs-redhat>
Component: selinux-policyAssignee: Daniel Walsh <dwalsh>
Status: CLOSED ERRATA QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 5.4CC: dwalsh, mmalik, syeghiay
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-01-20 21:30:25 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 Aleksander Adamowski 2008-08-18 12:18:12 UTC 
Description of problem:
When using the macro nscd_socket_use(DOMAIN) in custom modules, I no longer can compile them. I receive the following error:

ERROR 'permission ioctl is not defined for class sock_file' at token ';' on line 84001

and:

ERROR 'permission lock is not defined for class sock_file' at token ';' on line 84001

In the sources I can see this macro (defined in policy/modules/services/nscd.if) has the following line:

allow $1 nscd_var_run_t:sock_file rw_file_perms;

It seems that now rw_file_perms cannot be applied to sock_file class. There's a separate permissions macro for that now: 

define(`rw_sock_file_perms',`{ getattr read write append }')



Version-Release number of selected component (if applicable):
selinux-policy-strict-2.4.6-137.1.el5
Comment 1 Daniel Walsh 2008-08-20 10:59:37 UTC 
This is already fixed in U3 policy.

You can get a preview in 

http://people.redhat.com/dwalsh/SELinux/RHEL5
Comment 10 errata-xmlrpc 2009-01-20 21:30:25 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2009-0163.html