Bug 673038

Summary: FLASE POSITIVES WHEN KMEMLEAK TURNED ON
Product: Red Hat Enterprise Linux 6 Reporter: zhenzhong.duan
Component: kernelAssignee: Red Hat Kernel Manager <kernel-mgr>
Status: CLOSED WONTFIX QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.0CC: zhenzhong.duan
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-06 11:46:49 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
kmemleak file none

Description zhenzhong.duan 2011-01-27 06:36:55 UTC 
Description of problem:
@ On ca-ostest201 machine having OEL6-beta2-refresh-drop2 with
@ 2.6.32-44.2.el6.x86_64.debug kernel, I got following error message in dmesg
@ after reboot:
@ .
@ kmemleak: 1608 new suspected memory leaks (see /sys/kernel/debug/kmemleak)

Version-Release number of selected component (if applicable):


How reproducible:
everytime when boot up debug kernel

Steps to Reproduce:
1. turn on kmemleak support, 
2. boot up debug kernel, 
3. dmesg | grep kmemleak
  
Actual results:
about 1608 memory leak generated, kmemleak file save in attachment.

Expected results:
No leak or small leak.

Additional info:
Comment 1 zhenzhong.duan 2011-01-27 06:37:44 UTC 
Created attachment 475531 [details]
kmemleak file
Comment 3 RHEL Program Management 2011-02-01 06:22:45 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
Comment 4 RHEL Program Management 2011-02-01 19:11:32 UTC 
This request was erroneously denied for the current release of
Red Hat Enterprise Linux.  The error has been fixed and this
request has been re-proposed for the current release.
Comment 5 RHEL Program Management 2011-04-04 02:49:26 UTC 
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
Comment 6 RHEL Program Management 2011-10-07 15:21:27 UTC 
Since RHEL 6.2 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
Comment 7 Jan Kurik 2017-12-06 11:46:49 UTC 
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/