Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

+++ 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):
2.6.32.11-99 is where I see the issue
2.6.32.11-90 works fine.

How reproducible:
100%

Steps to Reproduce:
1. Boot using kernel 2.6.32.11-99
2. cat /proc/sys/vm/mmap_min_addr
  
Actual results:
ERROR permission denied

Expected results:
"0" or "4096" or whatever your configuration has.

Additional info:

--- Additional comment from cebbert on 2010-04-21 12:52:51 EDT ---

*** Bug 582810 has been marked as a duplicate of this bug. ***

--- Additional comment from eparis 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
inclusion.

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.