Bug 705640 - avc: denied { write } for yum-cache (livecd-creator)
Summary: avc: denied { write } for yum-cache (livecd-creator)
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy-targeted
Version: 13
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Miroslav Grepl
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-17 23:52 UTC by Mr-4
Modified: 2011-06-27 11:44 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-27 11:44:14 UTC
Type: ---


Attachments (Terms of Use)

Description Mr-4 2011-05-17 23:52:29 UTC
Description of problem:
I get the following avc when running kickstart to create system image:

type=AVC msg=audit(1305393466.885:31693): avc:  denied  { write } for  pid=3068 comm="mount" name="yum-cache" dev=dm-2 ino=1490 scontext=unconfined_u:unconfined_r:mount_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:livecd_tmp_t:s0 tclass=dir
type=SYSCALL msg=audit(1305393466.885:31693): arch=c000003e syscall=21 per=8 success=no exit=-13 a0=7f41aeb588e0 a1=2 a2=1000 a3=7fff6f5b9b10 items=0 ppid=3041 pid=3068 auid=500 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=pts0 ses=1 comm="mount" exe="/bin/mount" subj=unconfined_u:unconfined_r:mount_t:s0-s0:c0.c1023 key=(null)

This started happening fairly recently (may be after I installed the latest SELinux policy - .101) - never had this before!

Version-Release number of selected component (if applicable):
FC13, SELinux policy is the latest distributed for this revision (.101)

How reproducible:
Always

Steps to Reproduce:
1. from the console I execute: "setarch i386 livecd-creator -c ~/ks-dmz7.cfg -f dmz7.my.net"
2. After a few seconds I get the above avc. Attempts to start SELinux Troubleshooter (GUI front-end) also fail - miserably so (may be I should submit a separate bug about that too) - I get the troubleshooter icon appear at the bottom of the screen and then nothing happens, the icon is gone and neither does the troubleshooter appear!
3.
  
Actual results:
The above avc

Expected results:
No avc as I've never had that before!

Additional info:

Comment 1 Bug Zapper 2011-05-30 10:32:48 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Bug Zapper 2011-06-27 11:44:14 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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