Bug 220195 - selinux prevents mkinitrd from running properly
Summary: selinux prevents mkinitrd from running properly
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 6
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Daniel Walsh
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-12-19 16:40 UTC by Orion Poplawski
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version: 2.4.6-13
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-01-24 18:09:26 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Orion Poplawski 2006-12-19 16:40:48 UTC
Description of problem:

Ran "ssh hawk yum -y upgrade" to upgrade hawk.  This installed a new kernel. 
The initrd for this kernel was broken (didn't load scsi driver it needed to boot).

avcs: (duplicates eliminated)

Dec 19 09:12:44 hawk kernel: audit(1166544764.454:5656): avc:  denied  { read
write } for  pid=28625 comm="depmod" name="[6103353]" dev=sockfs ino=6103353
scontext=root:system_r:depmod_t:s0-s0:c0.c1023
tcontext=root:system_r:unconfined_t:s0-s0:c0.c1023 tclass=unix_stream_socket
Dec 19 09:12:45 hawk kernel: audit(1166544765.374:5658): avc:  denied  { read
write } for  pid=28626 comm="mkinitrd" name="[6103353]" dev=sockfs ino=6103353
scontext=root:system_r:bootloader_t:s0-s0:c0.c1023
tcontext=root:system_r:unconfined_t:s0-s0:c0.c1023 tclass=unix_stream_socket
Dec 19 09:12:56 hawk kernel: audit(1166544776.327:5660): avc:  denied  {
setfscreate } for  pid=29270 comm="cp"
scontext=root:system_r:bootloader_t:s0-s0:c0.c1023
tcontext=root:system_r:bootloader_t:s0-s0:c0.c1023 tclass=process

Version-Release number of selected component (if applicable):
selinux-policy-2.4.6-7.fc6


Ran mkinitrd by hand in ssh login session and that worked.

Comment 1 Daniel Walsh 2006-12-19 19:02:17 UTC
Fixed in selinux-policy-2.4.6-13

Comment 2 Orion Poplawski 2007-01-24 18:09:26 UTC
Confirmed fixed.


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