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.

Bug 1078319

Summary: core(5) man page shows wrong default value for coredump_filter
Product: Red Hat Enterprise Linux 6 Reporter: Marc Milgram <mmilgram>
Component: man-pages-overridesAssignee: Jan Chaloupka <jchaloup>
Status: CLOSED ERRATA QA Contact: Iveta Wiedermann <isenfeld>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.6CC: isenfeld, ovasik
Target Milestone: rcKeywords: ManPageChange, Patch
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: man page showed wrong default values for coredump_filter and incomplete descriptions of all bits. Consequence: incomplete and incorrect documentation Fix: description of missing bits added and default value corrected Result: correct documentation for coredump_filter
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-14 07:27:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1104125    

Description Marc Milgram 2014-03-19 15:25:13 UTC
Description of problem:
core(5) man page shows incorrect default value for coredump_filter.  It should show 0x33

Also, just above this point it lists meanings for bits 0-3, but there are meanings for bits 4-6.

Version-Release number of selected component (if applicable):
man-pages-3.22-20.el6.noarch

How reproducible:
100%

Steps to Reproduce:
1. man core
2. /coredump_filter

Actual results:
Shows following text:
           bit 0  Dump anonymous private mappings.
           bit 1  Dump anonymous shared mappings.
           bit 2  Dump file-backed private mappings.
           bit 3  Dump file-backed shared mappings.

       The default value of coredump_filter is 0x3; this reflects  traditional
       Linux  behavior  and  means  that  only  anonymous  memory segments are
       dumped.


Expected results:
Lists values for all relevant bits, and specifies the default value of coredump_filter is 0x33.

Additional info:
The remaining bits should be:
           bit 4  Dump ELF headers.
           bit 5  Dump huge pages that have private mappings
           bit 6  Dump huge pages that have shared mappings.

Comment 2 Peter Schiffer 2014-04-22 13:14:05 UTC
This is fixed in upstream, only backport is needed:
http://man7.org/linux/man-pages/man5/core.5.html

Comment 7 errata-xmlrpc 2014-10-14 07:27:06 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-1382.html