syzbot


WARNING: ODEBUG bug in bt_host_release

Status: upstream: reported syz repro on 2020/08/22 10:22
Reported-by: syzbot+f2639529f22768fab8a4@syzkaller.appspotmail.com
First crash: 1567d, last: 1011d
Fix bisection: failed (error log, bisect log)
  
Similar bugs (2)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream WARNING: ODEBUG bug in bt_host_release bluetooth syz done done 7 1333d 1586d 22/28 fixed on 2022/09/20 07:46
linux-4.19 WARNING: ODEBUG bug in bt_host_release 1 1394d 1394d 0/1 auto-closed as invalid on 2021/06/11 00:58
Last patch testing requests (2)
Created Duration User Patch Repo Result
2023/02/15 17:32 12m retest repro linux-4.14.y report log
2022/10/12 02:30 13m retest repro linux-4.14.y report log
Fix bisection attempts (19)
Created Duration User Patch Repo Result
2022/03/30 21:21 12m bisect fix linux-4.14.y error job log
2022/02/28 19:20 33m bisect fix linux-4.14.y OK (0) job log log
2022/01/29 18:49 30m bisect fix linux-4.14.y OK (0) job log log
2021/12/30 17:36 31m bisect fix linux-4.14.y OK (0) job log log
2021/11/30 16:33 38m bisect fix linux-4.14.y OK (0) job log log
2021/10/31 15:51 36m bisect fix linux-4.14.y OK (0) job log log
2021/09/25 00:04 32m bisect fix linux-4.14.y OK (0) job log log
2021/08/25 18:55 37m bisect fix linux-4.14.y OK (0) job log log
2021/07/26 17:38 29m bisect fix linux-4.14.y OK (0) job log log
2021/06/26 17:00 37m bisect fix linux-4.14.y OK (0) job log log
2021/05/27 16:27 33m bisect fix linux-4.14.y OK (0) job log log
2021/04/27 05:54 38m bisect fix linux-4.14.y OK (0) job log log
2021/03/27 12:45 32m bisect fix linux-4.14.y OK (0) job log log
2021/02/25 08:16 34m bisect fix linux-4.14.y OK (0) job log log
2021/01/25 10:03 33m bisect fix linux-4.14.y OK (0) job log log
2020/12/26 09:22 37m bisect fix linux-4.14.y OK (0) job log log
2020/11/26 08:49 32m bisect fix linux-4.14.y OK (0) job log log
2020/10/27 04:33 30m bisect fix linux-4.14.y OK (0) job log log
2020/09/27 04:00 32m bisect fix linux-4.14.y OK (0) job log log

Sample crash report:
IPv6: ADDRCONF(NETDEV_CHANGE): veth1_to_batadv: link becomes ready
Bluetooth: hci1 command 0x0409 tx timeout
Bluetooth: hci0 command 0x0c1a tx timeout
ODEBUG: free active (active state 0) object type: timer_list hint: delayed_work_timer_fn+0x0/0x90 kernel/workqueue.c:3144
------------[ cut here ]------------
WARNING: CPU: 1 PID: 27040 at lib/debugobjects.c:287 debug_print_object.cold+0xa7/0xdb lib/debugobjects.c:287
Kernel panic - not syncing: panic_on_warn set ...

CPU: 1 PID: 27040 Comm: syz-executor.0 Not tainted 4.14.194-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
 __dump_stack lib/dump_stack.c:17 [inline]
 dump_stack+0x1b2/0x283 lib/dump_stack.c:58
 panic+0x1f9/0x42d kernel/panic.c:183
 __warn.cold+0x20/0x4b kernel/panic.c:547
 report_bug+0x208/0x249 lib/bug.c:186
 fixup_bug arch/x86/kernel/traps.c:177 [inline]
 fixup_bug arch/x86/kernel/traps.c:172 [inline]
 do_error_trap+0x195/0x2d0 arch/x86/kernel/traps.c:295
 invalid_op+0x1b/0x40 arch/x86/entry/entry_64.S:964
RIP: 0010:debug_print_object.cold+0xa7/0xdb lib/debugobjects.c:287
RSP: 0018:ffff888097cd7b18 EFLAGS: 00010082
RAX: 0000000000000061 RBX: 0000000000000003 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff86ac12c0 RDI: ffffed1012f9af59
RBP: ffffffff86abc580 R08: 0000000000000061 R09: 0000000000000000
R10: 0000000000000000 R11: ffff8880a07d8540 R12: ffffffff813b7b30
R13: 0000000000000000 R14: ffff88809ea48680 R15: ffff88809bff7dc8
 __debug_check_no_obj_freed lib/debugobjects.c:747 [inline]
 debug_check_no_obj_freed+0x3b7/0x674 lib/debugobjects.c:776
 kfree+0xb9/0x250 mm/slab.c:3814
 bt_host_release+0x15/0x20 net/bluetooth/hci_sysfs.c:86
 device_release+0xf0/0x1a0 drivers/base/core.c:831
 kobject_cleanup lib/kobject.c:646 [inline]
 kobject_release lib/kobject.c:675 [inline]
 kref_put include/linux/kref.h:70 [inline]
 kobject_put+0x1f3/0x2d0 lib/kobject.c:692
 put_device+0x1c/0x30 drivers/base/core.c:2014
 vhci_release+0x78/0xe0 drivers/bluetooth/hci_vhci.c:355
 __fput+0x25f/0x7a0 fs/file_table.c:210
 task_work_run+0x11f/0x190 kernel/task_work.c:113
 exit_task_work include/linux/task_work.h:22 [inline]
 do_exit+0xa08/0x27f0 kernel/exit.c:865
 do_group_exit+0x100/0x2e0 kernel/exit.c:962
 SYSC_exit_group kernel/exit.c:973 [inline]
 SyS_exit_group+0x19/0x20 kernel/exit.c:971
 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
 entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x45d4d9
RSP: 002b:00007ffd036b4888 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 000000000045d4d9
RDX: 0000000000416d61 RSI: 00000000016a85f0 RDI: 0000000000000043
RBP: 00000000004c306d R08: 000000000000000b R09: 0000000000000000
R10: 00000000022f8940 R11: 0000000000000246 R12: 0000000000000007
R13: 00007ffd036b49d0 R14: 0000000000059961 R15: 00007ffd036b49e0

======================================================

Crashes (2):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2020/08/22 10:22 linux-4.14.y 6a24ca2506d6 6436ce4b .config console log report syz ci2-linux-4-14
2020/08/28 04:00 linux-4.14.y d7e78d08fa77 816e0689 .config console log report ci2-linux-4-14
* Struck through repros no longer work on HEAD.