From: "Miquel Sabaté Solà" <mssola@mssola.com>
To: kevin.xie@starfivetech.com
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Possible memory leaks in 'starfive_pcie_probe'
Date: Mon, 16 Feb 2026 00:16:57 +0100 [thread overview]
Message-ID: <87y0kta97a.fsf@> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 378 bytes --]
Hello,
I was testing the latest Linus' tree on my Starfive VisionFive2 board
when I realized that kmemleak was reporting on four suspected memory
leaks (see attachment).
I am not sure what to tell about what I was doing, since I wasn't doing
anything fancy, and my setup is quite minimal. But if you need any more
details I'm more than happy to provide them.
Cheers,
Miquel
[-- Attachment #1.2: leaks reported by kmemleak --]
[-- Type: text/plain, Size: 3423 bytes --]
unreferenced object 0xffffffd6e3942680 (size 128):
comm "(udev-worker)", pid 372, jiffies 4294905702
hex dump (first 32 bytes):
70 ef 15 b9 ff ff ff ff 40 ee 51 c1 d6 ff ff ff p.......@.Q.....
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
backtrace (crc 9489c4a7):
__create_object+0x2a/0xd8
kmemleak_alloc+0xb6/0xc8
__kmalloc_cache_noprof+0x3c6/0x510
request_threaded_irq+0x114/0x2e8
devm_request_threaded_irq+0x6e/0x188
plda_init_interrupts+0x2a6/0x5f0
plda_pcie_host_init+0x202/0x420
starfive_pcie_probe+0x2a8/0x490 [pcie_starfive]
platform_probe+0xb6/0x158
really_probe+0x180/0x8a8
__driver_probe_device+0x154/0x368
driver_probe_device+0x62/0x160
__driver_attach+0x192/0x510
bus_for_each_dev+0xe8/0x170
driver_attach+0x3c/0x60
bus_add_driver+0x2ac/0x570
unreferenced object 0xffffffd6e3942c80 (size 128):
comm "(udev-worker)", pid 372, jiffies 4294905703
hex dump (first 32 bytes):
70 ef 15 b9 ff ff ff ff 40 ee 51 c1 d6 ff ff ff p.......@.Q.....
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
backtrace (crc 836d6db5):
__create_object+0x2a/0xd8
kmemleak_alloc+0xb6/0xc8
__kmalloc_cache_noprof+0x3c6/0x510
request_threaded_irq+0x114/0x2e8
devm_request_threaded_irq+0x6e/0x188
plda_init_interrupts+0x2a6/0x5f0
plda_pcie_host_init+0x202/0x420
starfive_pcie_probe+0x2a8/0x490 [pcie_starfive]
platform_probe+0xb6/0x158
really_probe+0x180/0x8a8
__driver_probe_device+0x154/0x368
driver_probe_device+0x62/0x160
__driver_attach+0x192/0x510
bus_for_each_dev+0xe8/0x170
driver_attach+0x3c/0x60
bus_add_driver+0x2ac/0x570
unreferenced object 0xffffffd6e3943680 (size 128):
comm "(udev-worker)", pid 372, jiffies 4294905785
hex dump (first 32 bytes):
70 ef 15 b9 ff ff ff ff 40 be 51 c1 d6 ff ff ff p.......@.Q.....
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
backtrace (crc 414126a):
__create_object+0x2a/0xd8
kmemleak_alloc+0xb6/0xc8
__kmalloc_cache_noprof+0x3c6/0x510
request_threaded_irq+0x114/0x2e8
devm_request_threaded_irq+0x6e/0x188
plda_init_interrupts+0x2a6/0x5f0
plda_pcie_host_init+0x202/0x420
starfive_pcie_probe+0x2a8/0x490 [pcie_starfive]
platform_probe+0xb6/0x158
really_probe+0x180/0x8a8
__driver_probe_device+0x154/0x368
driver_probe_device+0x62/0x160
__driver_attach+0x192/0x510
bus_for_each_dev+0xe8/0x170
driver_attach+0x3c/0x60
bus_add_driver+0x2ac/0x570
unreferenced object 0xffffffd6e3943c80 (size 128):
comm "(udev-worker)", pid 372, jiffies 4294905785
hex dump (first 32 bytes):
70 ef 15 b9 ff ff ff ff 40 be 51 c1 d6 ff ff ff p.......@.Q.....
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
backtrace (crc c42897b8):
__create_object+0x2a/0xd8
kmemleak_alloc+0xb6/0xc8
__kmalloc_cache_noprof+0x3c6/0x510
request_threaded_irq+0x114/0x2e8
devm_request_threaded_irq+0x6e/0x188
plda_init_interrupts+0x2a6/0x5f0
plda_pcie_host_init+0x202/0x420
starfive_pcie_probe+0x2a8/0x490 [pcie_starfive]
platform_probe+0xb6/0x158
really_probe+0x180/0x8a8
__driver_probe_device+0x154/0x368
driver_probe_device+0x62/0x160
__driver_attach+0x192/0x510
bus_for_each_dev+0xe8/0x170
driver_attach+0x3c/0x60
bus_add_driver+0x2ac/0x570
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 897 bytes --]
reply other threads:[~2026-02-15 23:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87y0kta97a.fsf@ \
--to=mssola@mssola.com \
--cc=kevin.xie@starfivetech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.