From: Shuangpeng <shuangpeng.kernel@gmail.com>
To: mchehab@kernel.org
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [BUG] media: as102: kmemleak reports two leaks after dvb_register_frontend() failure
Date: Tue, 2 Jun 2026 16:38:07 -0400 [thread overview]
Message-ID: <DAD7161C-A1DA-422E-BBC5-2893ABDC2DD0@gmail.com> (raw)
Hi Kernel Maintainers,
I hit the following kmemleak reports while testing current upstream kernel:
kmemleak: unreferenced object in as102_usb_probe
kmemleak: unreferenced object in as102_attach
on commit: e8c2f9fdadee7cbc75134dc463c1e0d856d6e5c7 (May 25 2026)
The reproducer and .config files are here.
https://gist.github.com/shuangpengbai/f122f8acb8a9e4b9ed08d6a76dd5eb79
I’m happy to test debug patches or provide additional information.
Reported-by: Shuangpeng Bai <shuangpeng.kernel@gmail.com>
unreferenced object 0xffff88811641a000 (size 4096):
comm "kworker/1:1", pid 30, jiffies 4295053869
hex dump (first 32 bytes):
40 b3 2a 8b ff ff ff ff 00 70 47 66 81 88 ff ff @.*......pGf....
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
backtrace (crc 52c16f09):
__kmalloc_cache_noprof (./include/linux/kmemleak.h:44 mm/slub.c:4575 mm/slub.c:4899 mm/slub.c:5415)
as102_usb_probe (./include/linux/slab.h:950 ./include/linux/slab.h:1188 drivers/media/usb/as102/as102_usb_drv.c:348)
usb_probe_interface (drivers/usb/core/driver.c:396)
really_probe (drivers/base/dd.c:? drivers/base/dd.c:709)
__driver_probe_device (drivers/base/dd.c:871)
driver_probe_device (drivers/base/dd.c:901)
__device_attach_driver (drivers/base/dd.c:1029)
bus_for_each_drv (drivers/base/bus.c:500)
__device_attach (drivers/base/dd.c:1101)
device_initial_probe (drivers/base/dd.c:1156)
bus_probe_device (drivers/base/bus.c:613)
device_add (drivers/base/core.c:3706)
usb_set_configuration (drivers/usb/core/message.c:2268)
usb_generic_driver_probe (drivers/usb/core/generic.c:250)
usb_probe_device (drivers/usb/core/driver.c:291)
really_probe (drivers/base/dd.c:? drivers/base/dd.c:709)
unreferenced object 0xffff888166471000 (size 2048):
comm "kworker/1:1", pid 30, jiffies 4295053870
hex dump (first 32 bytes):
01 00 00 00 00 00 00 00 41 62 69 6c 69 73 20 53 ........Abilis S
79 73 74 65 6d 73 20 44 56 42 2d 54 69 74 61 6e ystems DVB-Titan
backtrace (crc f72415e5):
__kmalloc_cache_noprof (./include/linux/kmemleak.h:44 mm/slub.c:4575 mm/slub.c:4899 mm/slub.c:5415)
as102_attach (./include/linux/slab.h:950 ./include/linux/slab.h:1188 drivers/media/dvb-frontends/as102_fe.c:450)
as102_dvb_register (drivers/media/usb/as102/as102_drv.c:326)
as102_usb_probe (drivers/media/usb/as102/as102_usb_drv.c:397)
usb_probe_interface (drivers/usb/core/driver.c:396)
really_probe (drivers/base/dd.c:? drivers/base/dd.c:709)
__driver_probe_device (drivers/base/dd.c:871)
driver_probe_device (drivers/base/dd.c:901)
__device_attach_driver (drivers/base/dd.c:1029)
bus_for_each_drv (drivers/base/bus.c:500)
__device_attach (drivers/base/dd.c:1101)
device_initial_probe (drivers/base/dd.c:1156)
bus_probe_device (drivers/base/bus.c:613)
device_add (drivers/base/core.c:3706)
usb_set_configuration (drivers/usb/core/message.c:2268)
usb_generic_driver_probe (drivers/usb/core/generic.c:250)
Best,
Shuangpeng
next reply other threads:[~2026-06-02 20:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 20:38 Shuangpeng [this message]
2026-06-03 9:30 ` [PATCH 1/2] media: as102: fix memory leak in probe error path after device registration xiaopeitux
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=DAD7161C-A1DA-422E-BBC5-2893ABDC2DD0@gmail.com \
--to=shuangpeng.kernel@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@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
all inboxes | Powered by JetHome®