Bug 26293 - The shm filesystem should be mounted
Summary: The shm filesystem should be mounted
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: filesystem
Version: 7.1
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Aaron Brown
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-02-06 10:29 UTC by Christoph Rohland
Modified: 2014-03-17 02:18 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 2001-02-06 10:29:17 UTC


Attachments (Terms of Use)

Description Christoph Rohland 2001-02-06 10:29:14 UTC
glibc is looking for an instance of shm fs/swapfs for posix shared memory.
The SAP application server expects it at /dev/shm

Comment 1 Bill Nottingham 2001-02-06 18:26:00 UTC
The response from the kernel group is that this should *not* be mounted
automatically at boot; feel free to mount it if you need it.

Comment 2 Christoph Rohland 2001-02-06 19:34:45 UTC
Oh, I am suprised: I made the filesystem, worked with the glibc group that 
they use it for POSIX shm, the kernel docs say also it should be mounted, but 
you think it is not needed :-(

Comment 3 Bill Nottingham 2001-02-06 20:10:53 UTC
I believe there are concerns about it
a) working correctly
b) being used for simple DoS attacks

Comment 4 Christoph Rohland 2001-02-06 20:28:36 UTC
At a) You rely on SYSV shm in some applications? They use the same fs but 
kern_mounted. I am pretty sure it works better than any shm implementation we 
had in the 2.x timeframe.
At b) You could use the mount option nr_blocks, or on an -ac kernel the mount 
otion size to protect against that.


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