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.

Description of problem:
 While running the kernel-debug variant of 2.6.32-42.el6 I noticed the following message from dmesg:

kmemleak: 1631 new suspected memory leaks (see /sys/kernel/debug/kmemleak)

Version-Release number of selected component (if applicable):
2.6.32-42.el6

How reproducible:
Always 

Steps to Reproduce:
1. Boot the i386 2.6.32-42.el6 kernel-debug, run dmesg
  
Additional info:
Not sure of the actual impact of this message but it should be investigated to understand the potential leaks.

This is the only message that we get???

Larry

Probably should assign this to Jason at least until we figure out if there is a real problem and where it is.

Larry

This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release. It has
been denied for the current Red Hat Enterprise Linux release.

** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **

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.

Larry,
 I don't believe this is an issue any longer. Recent kernels have kmemleak disabled.

From dmesg:

 kmemleak: Kernel memory leak detector disabled

Best,
Jeff

Close because RHEL6 kernels have kmemleak disabled.

Larry