Bug 431270 - avc: denied { write } for pid=2911 comm="dmesg"
Summary: avc: denied { write } for pid=2911 comm="dmesg"
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: util-linux-ng
Version: 9
Hardware: x86_64
OS: Linux
low
low
Target Milestone: ---
Assignee: Karel Zak
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-02-01 21:39 UTC by Brock Organ
Modified: 2008-07-03 04:01 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-07-03 04:01:45 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Brock Organ 2008-02-01 21:39:58 UTC
* rawhide-20080201 i386
* General Installation / No SELinux denials in post-install system during boot

there are warnings of avc denials logged by the auditd daemon after starting a
freshly installed system:

> # dmesg | grep avc
> audit(1201900117.437:4): avc:  denied  { write } for  pid=2911 comm="dmesg" 
> path="/tmp/kate/stage2.2.conx2z/output" dev=dm-0 ino=4120587 
> scontext=system_u:system_r:dmesg_t:s0 
> tcontext=system_u:object_r:initrc_tmp_t:s0 tclass=file
> audit(1201900117.437:5): avc:  denied  { write } for  pid=2911 comm="dmesg" 
> path="/dev/tty12" dev=tmpfs ino=252 scontext=system_u:system_r:dmesg_t:s0 
> tcontext=system_u:object_r:tty_device_t:s0 tclass=chr_file
> # whereis dmesg

Comment 1 Karel Zak 2008-03-19 10:23:01 UTC
I guess this problem is fixed in the latest rawhide. Is it true?

Comment 2 Bug Zapper 2008-05-14 04:58:47 UTC
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 petrosyan 2008-07-03 04:01:45 UTC
The information we've requested above is required in order
to review this problem report further and diagnose or fix the
issue if it is still present.  Since it has been thirty days or
more since we first requested additional information, we're assuming
the problem is either no longer present in the current Fedora release, or
that there is no longer any interest in tracking the problem.

Setting status to "CLOSED INSUFFICIENT_DATA".  If you still
experience this problem after updating to our latest Fedora
release and can provide the information previously requested,
please feel free to reopen the bug report.

Thank you in advance.


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