[moderation] [kernel?] WARNING: ODEBUG bug in rtl8187_disconnect

1 view
Skip to first unread message

syzbot

unread,
7:08 AM (10 hours ago) 7:08 AM
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 6de23f81a5e0 Linux 7.0-rc1
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing
console output: https://syzkaller.appspot.com/x/log.txt?x=11369c4a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f1500201919951cc
dashboard link: https://syzkaller.appspot.com/bug?extid=b06fa6e5a057121d1459
compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
CC: [da...@kernel.org drive...@lists.linux.dev gre...@linuxfoundation.org linux-...@vger.kernel.org linu...@vger.kernel.org raf...@kernel.org]

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/0221dc407a97/disk-6de23f81.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/661e43e08c2b/vmlinux-6de23f81.xz
kernel image: https://storage.googleapis.com/syzbot-assets/590a5de7cbdb/bzImage-6de23f81.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+b06fa6...@syzkaller.appspotmail.com

------------[ cut here ]------------
ODEBUG: free active (active state 0) object: ffff888144d50030 object type: work_struct hint: cfg80211_rfkill_block_work+0x0/0x30 net/wireless/core.c:316
WARNING: lib/debugobjects.c:612 at debug_print_object+0x18e/0x2a0 lib/debugobjects.c:612, CPU#1: kworker/1:11/8825
Modules linked in:

CPU: 1 UID: 0 PID: 8825 Comm: kworker/1:11 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2026
Workqueue: usb_hub_wq hub_event
RIP: 0010:debug_print_object+0x19b/0x2a0 lib/debugobjects.c:612
Code: b8 00 00 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 80 3c 02 00 75 4f 48 8d 3d b2 7a 23 08 41 56 48 8b 14 dd e0 b5 af 87 4c 89 e6 <67> 48 0f b9 3a 58 83 05 0c 19 1f 08 01 48 83 c4 18 5b 5d 41 5c 41
RSP: 0018:ffffc9000161f468 EFLAGS: 00010246

RAX: dffffc0000000000 RBX: 0000000000000003 RCX: 0000000000000000
RDX: ffffffff87afb520 RSI: ffffffff87afb140 RDI: ffffffff8af45420
RBP: 0000000000000001 R08: ffff888144d50030 R09: ffffffff87888ca0
R10: 0000000000000001 R11: 0000000000000000 R12: ffffffff87afb140
R13: ffffffff87888ce0 R14: ffffffff8703b9a0 R15: ffffc9000161f568
FS: 0000000000000000(0000) GS:ffff8882687d3000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f78eb612000 CR3: 00000001210ec000 CR4: 00000000003506f0
Call Trace:
<TASK>
__debug_check_no_obj_freed lib/debugobjects.c:1099 [inline]
debug_check_no_obj_freed+0x4da/0x630 lib/debugobjects.c:1129
__free_pages_prepare mm/page_alloc.c:1440 [inline]
__free_frozen_pages+0x34e/0xfb0 mm/page_alloc.c:2978
device_release+0xa4/0x240 drivers/base/core.c:2565
kobject_cleanup lib/kobject.c:689 [inline]
kobject_release lib/kobject.c:720 [inline]
kref_put include/linux/kref.h:65 [inline]
kobject_put+0x1f7/0x640 lib/kobject.c:737
put_device+0x1f/0x30 drivers/base/core.c:3797
rtl8187_disconnect+0x117/0x160 drivers/net/wireless/realtek/rtl818x/rtl8187/dev.c:1690
usb_unbind_interface+0x1dd/0x9e0 drivers/usb/core/driver.c:458
device_remove drivers/base/dd.c:573 [inline]
device_remove+0x12a/0x180 drivers/base/dd.c:565
__device_release_driver drivers/base/dd.c:1284 [inline]
device_release_driver_internal+0x42e/0x600 drivers/base/dd.c:1307
bus_remove_device+0x22f/0x440 drivers/base/bus.c:616
device_del+0x376/0x9b0 drivers/base/core.c:3878
usb_disable_device+0x367/0x810 drivers/usb/core/message.c:1418
usb_disconnect+0x2e2/0x9a0 drivers/usb/core/hub.c:2345
hub_port_connect drivers/usb/core/hub.c:5407 [inline]
hub_port_connect_change drivers/usb/core/hub.c:5707 [inline]
port_event drivers/usb/core/hub.c:5871 [inline]
hub_event+0x1d0c/0x4af0 drivers/usb/core/hub.c:5953
process_one_work+0x9d7/0x1920 kernel/workqueue.c:3275
process_scheduled_works kernel/workqueue.c:3358 [inline]
worker_thread+0x5da/0xe40 kernel/workqueue.c:3439
kthread+0x370/0x450 kernel/kthread.c:467
ret_from_fork+0x6c3/0xcb0 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
</TASK>
----------------
Code disassembly (best guess):
0: b8 00 00 00 00 mov $0x0,%eax
5: 00 fc add %bh,%ah
7: ff lcall (bad)
8: df 48 89 fisttps -0x77(%rax)
b: fa cli
c: 48 c1 ea 03 shr $0x3,%rdx
10: 80 3c 02 00 cmpb $0x0,(%rdx,%rax,1)
14: 75 4f jne 0x65
16: 48 8d 3d b2 7a 23 08 lea 0x8237ab2(%rip),%rdi # 0x8237acf
1d: 41 56 push %r14
1f: 48 8b 14 dd e0 b5 af mov -0x78504a20(,%rbx,8),%rdx
26: 87
27: 4c 89 e6 mov %r12,%rsi
* 2a: 67 48 0f b9 3a ud1 (%edx),%rdi <-- trapping instruction
2f: 58 pop %rax
30: 83 05 0c 19 1f 08 01 addl $0x1,0x81f190c(%rip) # 0x81f1943
37: 48 83 c4 18 add $0x18,%rsp
3b: 5b pop %rbx
3c: 5d pop %rbp
3d: 41 5c pop %r12
3f: 41 rex.B


---
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
Reply all
Reply to author
Forward
0 new messages