> On 13 Mar 2026, at 11:18 AM, Nam Cao <[email protected]> wrote:
>
> Nilay Shroff <[email protected]> writes:
>> The kmemleak reports the following memory leak:
> ...
>> Fix this by retrieving the irq_data from the correct domain using
>> irq_domain_get_irq_data() and then accessing the chip_data via
>> irq_data_get_irq_chip_data().
>>
>> Cc: [email protected]
>> Fixes: cc0cc23babc9 ("powerpc/xive: Untangle xive from child interrupt
>> controller drivers")
>> Signed-off-by: Nilay Shroff <[email protected]>
Hi,
I have tested this patch, and it fixes the reported kmemleak issue.
Tested-by: Venkat Rao Bagalkote <[email protected]>
Below is the kmemleak output without this patch applied:
cat /sys/kernel/debug/kmemleak
unreferenced object 0xc00000000606fc80 (size 64):
comm "kworker/0:1", pid 11, jiffies 4294937450
hex dump (first 32 bytes):
01 00 00 00 00 00 00 00 00 00 ab 0d 00 04 00 00 ................
00 00 a1 80 00 00 0a c0 00 00 aa 0d 00 04 00 00 ................
backtrace (crc 642b8a1d):
__kmalloc_cache_noprof+0x350/0x7a4
xive_irq_alloc_data.constprop.0+0x40/0xe0
xive_irq_domain_alloc+0xd4/0x1ac
irq_domain_alloc_irqs_parent+0x44/0x6c
pseries_irq_domain_alloc+0x1c4/0x34c
irq_domain_alloc_irqs_parent+0x44/0x6c
msi_domain_alloc+0xb0/0x214
irq_domain_alloc_irqs_locked+0x138/0x4d0
__irq_domain_alloc_irqs+0x8c/0xfc
__msi_domain_alloc_irqs+0x214/0x4c8
msi_domain_alloc_irqs_all_locked+0x70/0xf8
pci_msi_setup_msi_irqs+0x60/0x78
msix_setup_interrupts+0x17c/0x318
__pci_enable_msix_range+0x41c/0x770
pci_alloc_irq_vectors_affinity+0x170/0x1d8
nvme_pci_enable+0xa0/0x3b0 [nvme]
unreferenced object 0xc00000000606f900 (size 64):
comm "kworker/0:1", pid 11, jiffies 4294937451
With the patch applied, no kmemleak reports are observed after repeated MSI‑X
enable/disable cycles on the NVMe controller.
Regards,
Venkat
> Reviewed-by: Nam Cao <[email protected]>
>
