1464311 – kmemleak for mdadm

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 1464311 - kmemleak for mdadm

Summary: kmemleak for mdadm

Keywords:
Status:	CLOSED NOTABUG
Alias:	None
Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	mdadm
Sub Component:
Version:	7.4
Hardware:	Unspecified
OS:	Unspecified
Priority:	unspecified
Severity:	unspecified
Target Milestone:	rc
Target Release:	---
Assignee:	Kernel Drivers
QA Contact:	guazhang@redhat.com
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2017-06-23 04:12 UTC by Zhang Yi
Modified:	2017-06-23 05:18 UTC (History)
CC List:	3 users (show)
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:	2017-06-23 05:18:28 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)
output for /sys/kernel/debug/kmemleak (133.33 KB, text/plain) 2017-06-23 04:12 UTC, Zhang Yi	no flags	Details
View All

Description Zhang Yi 2017-06-23 04:12:15 UTC

Created attachment 1290880 [details]
output for /sys/kernel/debug/kmemleak

Description of problem:
mdadm kmemleak

Version-Release number of selected component (if applicable):
mdadm-4.0-5.el7.ppc64
3.10.0-686.el7.ppc64.debug

How reproducible:


Steps to Reproduce:
run mdadm grow-add-disk case

here is the beaker job:
https://beaker.engineering.redhat.com/jobs/1919619

Actual results:


Expected results:


Additional info:

unreferenced object 0xc0000003df1b0d40 (size 64):
  comm "mdadm", pid 30429, jiffies 4295287850 (age 1492.800s)
  hex dump (first 32 bytes):
    c0 00 00 03 df 1b 0d 40 c0 00 00 03 df 1b 0d 40  .......@.......@
    c0 00 00 00 01 ad 2c 00 00 00 00 00 00 00 00 00  ......,.........
  backtrace:
    [<c0000000006bdedc>] .devres_alloc_node+0x2c/0x70
    [<c00000000002a578>] .arch_dma_init+0x58/0x70
    [<c0000000006b2d54>] .device_add+0x184/0xaa0
    [<c0000000005391d4>] .add_disk+0x244/0x630
    [<c000000000814bd8>] .md_probe+0x218/0x360
    [<c0000000006bdc5c>] .kobj_lookup+0x13c/0x1f0
    [<c00000000053822c>] .get_gendisk+0x4c/0x210
    [<c0000000003ed9b0>] .blkdev_get+0x80/0x440
    [<c000000000373ae4>] .vfs_open+0x2b4/0x480
    [<c00000000039151c>] .do_last+0x48c/0x11b0
    [<c000000000396284>] .path_openat+0x274/0xd30
    [<c000000000398130>] .do_filp_open+0x40/0xb0
    [<c000000000376078>] .SyS_open+0x128/0x270
    [<c00000000000a190>] system_call+0x38/0xb4

Note You need to log in before you can comment on or make changes to this bug.