From: syzbot <syzbot+87ce68d9f48eca96a84a@syzkaller.appspotmail.com>
To: drifabdelmalekmohamedsaid@gmail.com,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [kernel?] memory leak in dev_set_name
Date: Sat, 26 Sep 2026 04:25:01 -0700 [thread overview]
Message-ID: <6ab7ab8d.80e1c6cc.1e8e5f.0043.GAE@google.com> (raw)
In-Reply-To: <CA+xk8n9mG-FZ+0Xg5L-GSL2y8KJ+6CBvkXVKCvyJGzgeX+_qFg@mail.gmail.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
memory leak in device_set_deferred_probe_reason
BUG: memory leak
unreferenced object 0xffff888126289b00 (size 64):
comm "syz.0.305", pid 7769, jiffies 4294969835
hex dump (first 32 bytes):
67 61 64 67 65 74 3a 20 44 65 76 69 63 65 20 6e gadget: Device n
6f 74 20 72 65 61 64 79 20 74 6f 20 70 72 6f 62 ot ready to prob
backtrace (crc 2d586e63):
kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
slab_post_alloc_hook mm/slub.c:4696 [inline]
slab_alloc_node mm/slub.c:4996 [inline]
__do_kmalloc_node mm/slub.c:5413 [inline]
__kmalloc_node_track_caller_noprof+0x40d/0x560 mm/slub.c:5545
kvasprintf+0x6e/0xf0 lib/kasprintf.c:25
kasprintf+0x6b/0x90 lib/kasprintf.c:59
device_set_deferred_probe_reason+0x41/0x70 drivers/base/dd.c:235
__dev_probe_failed+0xae/0xc0 drivers/base/core.c:5096
dev_err_probe+0x73/0xa0 drivers/base/core.c:5156
__driver_probe_device+0x185/0x1a0 drivers/base/dd.c:846
driver_probe_device+0x28/0xf0 drivers/base/dd.c:898
__driver_attach drivers/base/dd.c:1292 [inline]
__driver_attach+0x10a/0x200 drivers/base/dd.c:1232
bus_for_each_dev+0xb8/0x120 drivers/base/bus.c:383
bus_add_driver+0x122/0x280 drivers/base/bus.c:763
driver_register+0xb1/0x140 drivers/base/driver.c:174
usb_gadget_register_driver_owner+0x69/0xe0 drivers/usb/gadget/udc/core.c:1752
gadget_dev_desc_UDC_store+0x153/0x1e0 drivers/usb/gadget/configfs.c:300
flush_write_buffer fs/configfs/file.c:207 [inline]
configfs_write_iter+0x10d/0x1a0 fs/configfs/file.c:229
new_sync_write fs/read_write.c:595 [inline]
vfs_write+0x3ae/0x720 fs/read_write.c:687
connection error: failed to recv *flatrpc.ExecutorMessageRawT: EOF
Tested on:
commit: 6812ce4e Merge tag 'drm-fixes-2026-09-26' of https://g..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=133592c9580000
kernel config: https://syzkaller.appspot.com/x/.config?x=5006f84926c45769
dashboard link: https://syzkaller.appspot.com/bug?extid=87ce68d9f48eca96a84a
compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
patch: https://syzkaller.appspot.com/x/patch.diff?x=14146a05580000
next parent reply other threads:[~2026-09-26 11:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+xk8n9mG-FZ+0Xg5L-GSL2y8KJ+6CBvkXVKCvyJGzgeX+_qFg@mail.gmail.com>
2026-09-26 11:25 ` syzbot [this message]
2026-08-10 17:13 syzbot
2026-08-11 4:04 ` Edward Adam Davis
2026-08-11 13:32 ` syzbot
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=6ab7ab8d.80e1c6cc.1e8e5f.0043.GAE@google.com \
--to=syzbot+87ce68d9f48eca96a84a@syzkaller.appspotmail.com \
--cc=drifabdelmalekmohamedsaid@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/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®