+++ This bug was initially created as a clone of Bug #583292 +++
Description of problem:
Despite the permissions showing global read access, /proc/sys/vm/mmap_min_addr can not be read by normal users.
Version-Release number of selected component (if applicable):
220.127.116.11-99 is where I see the issue
18.104.22.168-90 works fine.
Steps to Reproduce:
1. Boot using kernel 22.214.171.124-99
2. cat /proc/sys/vm/mmap_min_addr
ERROR permission denied
"0" or "4096" or whatever your configuration has.
--- Additional comment from email@example.com on 2010-04-21 12:52:51 EDT ---
*** Bug 582810 has been marked as a duplicate of this bug. ***
--- Additional comment from firstname.lastname@example.org on 2010-05-14 16:00:30 EDT ---
fixed upstream in 2.6.34. If you need this in an older kernel please reopen this bug and I can backport.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
Patch(es) available on kernel-2.6.32-28.el6
This also regressed in 2.16.18 kernel on RHEL 5 between 2.6.18-164.15 and 2.6.18-194.3 kernel. Exact same symptom as described here.
It broke "bitbake" for OpenEmbedded development.
I cloned the original Bug #583292 to Bug #623519 against RHEL 5.
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.