From: Madhavan Srinivasan <maddy@linux.ibm.com>
To: linuxppc-dev@lists.ozlabs.org, Nilay Shroff <nilay@linux.ibm.com>
Cc: namcao@linutronix.de, mpe@ellerman.id.au, npiggin@gmail.com,
maz@kernel.org, ritesh.list@gmail.com, gautam@linux.ibm.com,
stable@vger.kernel.org, Christophe Leroy <chleroy@kernel.org>,
Thomas Gleixner <tglx@kernel.org>
Subject: Re: [PATCH] powerpc/xive: fix kmemleak caused by incorrect chip_data lookup
Date: Wed, 8 Apr 2026 09:58:54 +0530 [thread overview]
Message-ID: <177562236416.1381144.5101696715064742344.b4-ty@linux.ibm.com> (raw)
In-Reply-To: <20260311134336.326996-1-nilay@linux.ibm.com>
On Wed, 11 Mar 2026 19:13:31 +0530, Nilay Shroff wrote:
> The kmemleak reports the following memory leak:
>
> Unreferenced object 0xc0000002a7fbc640 (size 64):
> comm "kworker/8:1", pid 540, jiffies 4294937872
> hex dump (first 32 bytes):
> 01 00 00 00 00 00 00 00 00 00 09 04 00 04 00 00 ................
> 00 00 a7 81 00 00 0a c0 00 00 08 04 00 04 00 00 ................
> backtrace (crc 177d48f6):
> __kmalloc_cache_noprof+0x520/0x730
> xive_irq_alloc_data.constprop.0+0x40/0xe0
> xive_irq_domain_alloc+0xd0/0x1b0
> irq_domain_alloc_irqs_parent+0x44/0x6c
> pseries_irq_domain_alloc+0x1cc/0x354
> irq_domain_alloc_irqs_parent+0x44/0x6c
> msi_domain_alloc+0xb0/0x220
> irq_domain_alloc_irqs_locked+0x138/0x4d0
> __irq_domain_alloc_irqs+0x8c/0xfc
> __msi_domain_alloc_irqs+0x214/0x4d8
> msi_domain_alloc_irqs_all_locked+0x70/0xf8
> pci_msi_setup_msi_irqs+0x60/0x78
> __pci_enable_msix_range+0x54c/0x98c
> pci_alloc_irq_vectors_affinity+0x16c/0x1d4
> nvme_pci_enable+0xac/0x9c0 [nvme]
> nvme_probe+0x340/0x764 [nvme]
>
> [...]
Applied to powerpc/next.
[1/1] powerpc/xive: fix kmemleak caused by incorrect chip_data lookup
https://git.kernel.org/powerpc/c/6771c54728c278bf1e4bfdab4fddbbb186e33498
cheers
prev parent reply other threads:[~2026-04-08 4:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 13:43 [PATCH] powerpc/xive: fix kmemleak caused by incorrect chip_data lookup Nilay Shroff
2026-03-13 5:48 ` Nam Cao
2026-03-13 7:23 ` Venkat
2026-04-08 4:28 ` Madhavan Srinivasan [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=177562236416.1381144.5101696715064742344.b4-ty@linux.ibm.com \
--to=maddy@linux.ibm.com \
--cc=chleroy@kernel.org \
--cc=gautam@linux.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maz@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=namcao@linutronix.de \
--cc=nilay@linux.ibm.com \
--cc=npiggin@gmail.com \
--cc=ritesh.list@gmail.com \
--cc=stable@vger.kernel.org \
--cc=tglx@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox