Red Hat Bugzilla – Bug 145892
mqueue filesystem must be mounted
Last modified: 2014-03-16 22:52:04 EDT
Description of problem:
The mqueue pseudo filesystem provides the only means to inspect
currently created POSIX message queues. Not having it mounted would
be equivalent to not having the ipcs program for SysV IPC.
Unprivileged users could allocate resources without the sysadmin
knowing. Uncleanly terminated processes leave behind garbage which
cannot be cleaned up.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.create POSIX message queue
2.try to find it outside the process
ls -l /dev/mqueue should show it
I think it's anaconda's job. A new line in /etc/fstab should be
created during the installation/update process.
none /dev/mqueue mqueue noexec 0 0
This also should go into RHEL4.
I'd rather do this more generically than having to continue to do it for every
kernel filesystem type that gets added. Especially as otherwise, people won't
get them on upgrades
*** Bug 140809 has been marked as a duplicate of this bug. ***
A solution we're considering is a separate fstab.sys for 'system' filesystems
(such as /proc, /sys, /selinux, /dev/pts, /dev/mqueue). This would be a packaged
file that could be updated easily without %post hackery.
This would break something looking in fstab for where /proc is (or should be)
mounted. Arguably, something looking at it for where something is mounted is
broken (and should be looking at a) mtab b) /proc/mounts.)
What this will change is the behavior of umount -a/mount -a. Whether these sorts
of filesystems should follow the same behavior there should be considered.
If you go the route with a separate file, don't special case it. Do it as we do
in many such cases:
1. create a directory /etc/fstab.d
2. install files such as /etc/fstab.d/system in it
Then other packages can do similar things. We see new special-purpose
filesystems all the time.
Based on the date this bug was created, it appears to have been reported
against rawhide during the development of a Fedora release that is no
longer maintained. In order to refocus our efforts as a project we are
flagging all of the open bugs for releases which are no longer
maintained. If this bug remains in NEEDINFO thirty (30) days from now,
we will automatically close it.
If you can reproduce this bug in a maintained Fedora version (7, 8, or
rawhide), please change this bug to the respective version and change
the status to ASSIGNED. (If you're unable to change the bug's version
or status, add a comment to the bug and someone will change it for you.)
Thanks for your help, and we apologize again that we haven't handled
these issues to this point.
The process we're following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
This is still a problem. It has to be fixed as explained before.
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9. 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 '9'.
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 9'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 9 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:
This is fixed in F-16.