Bug 171659 - access denied messages for an LVM swap device
Summary: access denied messages for an LVM swap device
Status: CLOSED DUPLICATE of bug 169427
Alias: None
Product: Fedora
Classification: Fedora
Component: mkinitrd
Version: 5
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Dave Jones
QA Contact: Brian Brock
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-10-24 21:17 UTC by Brian G. Anderson
Modified: 2015-01-04 22:22 UTC (History)
3 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2006-09-13 19:31:02 UTC


Attachments (Terms of Use)
output of allow2why (13.31 KB, text/plain)
2005-10-24 21:17 UTC, Brian G. Anderson
no flags Details
output of audit2allow (397 bytes, text/plain)
2005-10-24 21:18 UTC, Brian G. Anderson
no flags Details

Description Brian G. Anderson 2005-10-24 21:17:13 UTC
Description of problem:
my /var/log/messages file gets a log of selinux access messages about denied
access to "VolGroup00-LogVol01".  This is the machines swap device which resides
on a LVM device.  There are two other logical volumes:  LogVol00 is / and
LogVol02 is /home.  Neither of these volumes get any selinux mesages.


Version-Release number of selected component (if applicable):
selinux-policy-targeted 1.27.2-1


How reproducible:
every boot.


Steps to Reproduce:
1.boot system
2.
3.
  
Actual results:
numerous access denied messages.


Expected results:


Additional info:

I've attached the results of running /var/log/messages through audit2why and
audit2allow.

Comment 1 Brian G. Anderson 2005-10-24 21:17:13 UTC
Created attachment 120321 [details]
output of allow2why

Comment 2 Brian G. Anderson 2005-10-24 21:18:59 UTC
Created attachment 120322 [details]
output of audit2allow

Comment 3 Daniel Walsh 2005-10-24 21:50:59 UTC
This is caused because the kernel or some other early app is leaking a file
descriptor.

Comment 4 Michal Jaegermann 2005-10-28 16:28:56 UTC
See bug #169427.  Does it ring a bell?  Even if "left open" message is
supressed in some versions I do not think that the problem is gone.

Comment 5 Alasdair Kergon 2006-09-13 19:31:02 UTC

*** This bug has been marked as a duplicate of 169427 ***


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