Hello,
syzbot found the following issue on:
HEAD commit: 1a8763b93150 Linux 6.1.188
git tree: linux-6.1.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=13796501580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=31dfefc4a14efea3
dashboard link:
https://syzkaller.appspot.com/bug?extid=e00027c36301c05fe58d
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/be5de8c5e41e/disk-1a8763b9.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/b803e8d05dd4/vmlinux-1a8763b9.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/723f53728c4f/bzImage-1a8763b9.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+e00027...@syzkaller.appspotmail.com
------------[ cut here ]------------
sysfs group 'byte_queue_limits' not found for kobject 'tx-0'
WARNING: CPU: 0 PID: 6036 at fs/sysfs/group.c:280 sysfs_remove_group+0x177/0x290 fs/sysfs/group.c:278
Modules linked in:
CPU: 0 PID: 6036 Comm: kworker/0:11 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Workqueue: events delete_netdev
RIP: 0010:sysfs_remove_group+0x177/0x290 fs/sysfs/group.c:278
Code: 8b 1b 4c 89 f8 48 c1 e8 03 42 80 3c 28 00 74 08 4c 89 ff e8 eb 2b cb ff 49 8b 17 48 c7 c7 a0 70 9c 8a 48 89 de e8 f9 6d 45 ff <0f> 0b 48 83 c4 08 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 03 e7 79 ff
RSP: 0018:ffffc9000d7f78e0 EFLAGS: 00010246
RAX: 9a36d20a68ecf100 RBX: ffffffff8b8c2f40 RCX: ffff88802f26da00
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000002
RBP: 000000000000008a R08: ffffc9000d7f75e7 R09: 1ffff92001afeebc
R10: dffffc0000000000 R11: fffff52001afeebd R12: 1ffffffff17184fc
R13: dffffc0000000000 R14: ffff8880572f30e8 R15: ffff888059675020
FS: 0000000000000000(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000200000000000 CR3: 000000004a197000 CR4: 00000000003506f0
Call Trace:
<TASK>
netdev_queue_update_kobjects+0x3dd/0x480 net/core/net-sysfs.c:1729
remove_queue_kobjects net/core/net-sysfs.c:1828 [inline]
netdev_unregister_kobject+0x104/0x250 net/core/net-sysfs.c:1981
unregister_netdevice_many_notify+0x14b6/0x1990 net/core/dev.c:11051
unregister_netdevice_many net/core/dev.c:11077 [inline]
unregister_netdevice_queue+0x2e5/0x330 net/core/dev.c:10960
unregister_netdevice include/linux/netdevice.h:3077 [inline]
lowpan_unregister_netdevice net/6lowpan/core.c:66 [inline]
lowpan_unregister_netdev+0x18/0x20 net/6lowpan/core.c:74
unregister_dev+0x70/0x1a0 net/bluetooth/6lowpan.c:763
process_one_work+0x8ab/0x1160 kernel/workqueue.c:2292
worker_thread+0xaf5/0x12a0 kernel/workqueue.c:2439
kthread+0x29d/0x330 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</TASK>
---
This report is generated by a bot. It may contain errors.
See
https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at
syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup