Bug 528064 - mcelog AVC denial
Summary: mcelog AVC denial
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: mcelog
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jon Masters
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-10-08 19:40 UTC by Jerry James
Modified: 2009-10-22 19:16 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-10-22 19:16:46 UTC
Type: ---


Attachments (Terms of Use)

Description Jerry James 2009-10-08 19:40:11 UTC
Description of problem:
Thanks for the mcelog update.  Now, instead of getting email once per hour about the record length mismatch, I'm getting email once per hour saying "mcelog: Cannot open /dev/mem for DMI decoding: Permission denied". :-)  At the same time, setroubleshoot reports an AVC denial.  Here is a sample:

node=localhost.localdomain type=AVC msg=audit(1255028461.197:22962): avc: denied {read} for pid=4650 comm="mcelog" name="mem" dev=tmpfs ino=3086 scontext=system_u:system_r:dmesg_t:s0-s0:c0.c1023 tcontext=system_u:object_r:memory_device_t:s0 tclass=chr_file

node=localhost.localdomain type=SYSCALL msg=audit(1255028461.197:22962): arch=c000003e syscall=2 success=yes exit=0 a0=409e28 a1=0 a2=1000 a3=2 items=0 ppid=4649 pid=4650 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=5 comm="mcelog" exe="/usr/sbin/mcelog" subj=system_u:system_r:dmesg_t:s0-s0:c0.c1023 key=(null)

Version-Release number of selected component (if applicable):
mcelog-0.9pre1-0.1.fc12.x86_64

How reproducible:
Once per hour.

Steps to Reproduce:
1. Install mcelog
2. Wait an hour
  
Actual results:
mcelog does not have permission to access /dev/mem and so reports failure.  Additionally, setroubleshoot reports the failure.

Expected results:
mcelog runs without errors.

Additional info:

Comment 1 Jerry James 2009-10-22 19:16:46 UTC
A subsequent update appears to have fixed this.


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