Bug 692730 - /selinux mount device shows as "none"
Summary: /selinux mount device shows as "none"
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: libselinux
Version: 15
Hardware: All
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Daniel Walsh
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-31 23:34 UTC by Cesar Eduardo Barros
Modified: 2012-07-27 13:22 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-07-27 13:22:29 UTC
Type: ---

Attachments (Terms of Use)
Proposed patch (untested) (1.23 KB, patch)
2011-03-31 23:34 UTC, Cesar Eduardo Barros 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Description Cesar Eduardo Barros 2011-03-31 23:34:45 UTC 
Created attachment 489265 [details]
Proposed patch (untested)

Description of problem:

The mount output for /selinux shows as:

none on /selinux type selinuxfs (rw,relatime)

It would be slightly more readable if it were something like:

selinuxfs on /selinux type selinuxfs (rw,relatime)

/selinux is currently the only one on the mount output to use "none". IIRC, a similar change was made to the mount of /proc many years ago.


Version-Release number of selected component (if applicable):

libselinux-2.0.98-2.fc15.i686

How reproducible:

Always.

Steps to Reproduce:

Boot with selinux enabled.
  
Actual results:

none on /selinux type selinuxfs (rw,relatime)

Expected results:

Something better than "none".

Additional info:
Comment 1 Cesar Eduardo Barros 2011-03-31 23:36:22 UTC 
Comment on attachment 489265 [details]
Proposed patch (untested)

Fix attachment details
Comment 2 Daniel Walsh 2012-07-27 13:22:29 UTC 
Since this version of Fedora is no longer supported I am closing this bugs.  If you are still seeing this bug in a current version of fedora, please reopen the bugzilla with the appropriate version number.
Note You need to log in before you can comment on or make changes to this bug.