Bug 561574 - ypbind gets "avc: denied { getsched }"
Summary: ypbind gets "avc: denied { getsched }"
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 12
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Miroslav Grepl
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-02-03 23:08 UTC by Josh Stone
Modified: 2010-03-04 00:14 UTC (History)
3 users (show)

Fixed In Version: selinux-policy-3.6.32-92.fc12
Clone Of:
Environment:
Last Closed: 2010-03-04 00:14:25 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Josh Stone 2010-02-03 23:08:48 UTC
Description of problem:
ypbind is crashing when selinux is enabled.

Version-Release number of selected component (if applicable):
ypbind-1.31-2.fc13.x86_64
selinux-policy-3.7.8-6.fc13.noarch

How reproducible:
100%

Steps to Reproduce:
1. service ypbind start
2. service ypbind status
3.
  
Actual results:
The service-start takes a while and then claims to be OK, but service-status says "ypbind dead but pid file exists".

Expected results:
ypbind stays alive and does its job. :)

Additional info:

From dmesg I see:
type=1400 audit(1265236293.793:11424): avc:  denied  { getsched } for  pid=1302 comm="ypbind" scontext=unconfined_u:system_r:ypbind_t:s0 tcontext=unconfined_u:system_r:ypbind_t:s0 tclass=process
type=1400 audit(1265236293.793:11425): avc:  denied  { getsched } for  pid=1302 comm="ypbind" scontext=unconfined_u:system_r:ypbind_t:s0 tcontext=unconfined_u:system_r:ypbind_t:s0 tclass=process
ypbind[1302] trap int3 ip:3f2dc44292 sp:7f4278afd860 error:0

This was on x86_64.  On i686 I get the same failure, with the same two AVCs but not the "trap int3" message.

Everything works fine if I:
    setenforce 0 && service ypbind start && setenforce 1

Comment 1 Karel Klíč 2010-02-16 15:23:31 UTC
Shouldn't getsched be allowed for multithreaded programs (ypbind is multithreaded)?

Comment 2 Daniel Walsh 2010-02-16 15:44:12 UTC
Yes,  Sorry we missed this one.

Miroslav can you add it.

Comment 3 Miroslav Grepl 2010-02-16 15:52:30 UTC
Fixed in selinux-policy-3.6.32-91.fc12

Comment 4 Josh Stone 2010-02-16 16:56:47 UTC
(In reply to comment #3)
> Fixed in selinux-policy-3.6.32-91.fc12    

I haven't had any trouble on 12, just on 13.  Are you sending a fix there too?

Comment 5 Daniel Walsh 2010-02-16 18:08:21 UTC
Josh yes
Fixed in selinux-policy-3.7.9-1.fc13

Comment 6 Fedora Update System 2010-02-23 20:55:15 UTC
selinux-policy-3.6.32-92.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/selinux-policy-3.6.32-92.fc12

Comment 7 Fedora Update System 2010-02-26 03:41:51 UTC
selinux-policy-3.6.32-92.fc12 has been pushed to the Fedora 12 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update selinux-policy'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2010-2953

Comment 8 Fedora Update System 2010-03-04 00:10:36 UTC
selinux-policy-3.6.32-92.fc12 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.