WARNING: ODEBUG bug in cancel_delayed_work

7 views
Skip to first unread message

syzbot

unread,
Jul 30, 2020, 2:39:28 PM7/30/20
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 205a42ce Linux 4.19.135
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=127cf56c900000
kernel config: https://syzkaller.appspot.com/x/.config?x=155b0b328eb5e700
dashboard link: https://syzkaller.appspot.com/bug?extid=816b6c4630ff3b31e09d
compiler: gcc (GCC) 10.1.0-syz 20200507
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=113e60d0900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12a96c5c900000

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

IPVS: ftp: loaded support on port[0] = 21
Bluetooth: hci0: command 0x0409 tx timeout
Bluetooth: hci0: command 0x041b tx timeout
------------[ cut here ]------------
ODEBUG: assert_init not available (active state 0) object type: timer_list hint: (null)
WARNING: CPU: 0 PID: 6505 at lib/debugobjects.c:325 debug_print_object+0x160/0x250 lib/debugobjects.c:325
Kernel panic - not syncing: panic_on_warn set ...

CPU: 0 PID: 6505 Comm: syz-executor267 Not tainted 4.19.135-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1fc/0x2fe lib/dump_stack.c:118
panic+0x26a/0x50e kernel/panic.c:186
__warn.cold+0x20/0x61 kernel/panic.c:541
report_bug+0x262/0x2b0 lib/bug.c:186
fixup_bug arch/x86/kernel/traps.c:178 [inline]
fixup_bug arch/x86/kernel/traps.c:173 [inline]
do_error_trap+0x1d7/0x310 arch/x86/kernel/traps.c:296
invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:1038
RIP: 0010:debug_print_object+0x160/0x250 lib/debugobjects.c:325
Code: dd 40 13 cb 87 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 bf 00 00 00 48 8b 14 dd 40 13 cb 87 48 c7 c7 c0 08 cb 87 e8 db 0d dd fd <0f> 0b 83 05 e3 0c 4e 06 01 48 83 c4 20 5b 5d 41 5c 41 5d c3 48 89
RSP: 0018:ffff8880896974d8 EFLAGS: 00010086
RAX: 0000000000000000 RBX: 0000000000000005 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff8154cf01 RDI: ffffed10112d2e8d
RBP: 0000000000000001 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000005 R11: ffffffff8ad3601b R12: ffffffff88da08e0
R13: ffffffff815a2ad0 R14: ffff8880848876a8 R15: 1ffff110112d2ea6
debug_object_assert_init lib/debugobjects.c:694 [inline]
debug_object_assert_init+0x1f0/0x2e0 lib/debugobjects.c:665
debug_timer_assert_init kernel/time/timer.c:732 [inline]
debug_assert_init kernel/time/timer.c:784 [inline]
del_timer+0x6d/0x100 kernel/time/timer.c:1209
try_to_grab_pending+0x2b6/0x6f0 kernel/workqueue.c:1223
__cancel_work kernel/workqueue.c:3103 [inline]
cancel_delayed_work+0x76/0x2c0 kernel/workqueue.c:3132
l2cap_clear_timer include/net/bluetooth/l2cap.h:832 [inline]
l2cap_chan_del+0x53a/0x8e0 net/bluetooth/l2cap_core.c:638
l2cap_chan_close+0x108/0x820 net/bluetooth/l2cap_core.c:754
l2cap_sock_shutdown+0x85e/0xbd0 net/bluetooth/l2cap_sock.c:1159
l2cap_sock_release+0x63/0x190 net/bluetooth/l2cap_sock.c:1201
__sock_release+0xcd/0x2a0 net/socket.c:579
sock_close+0x15/0x20 net/socket.c:1140
__fput+0x2ce/0x890 fs/file_table.c:278
task_work_run+0x148/0x1c0 kernel/task_work.c:113
exit_task_work include/linux/task_work.h:22 [inline]
do_exit+0xbb2/0x2b70 kernel/exit.c:887
do_group_exit+0x125/0x310 kernel/exit.c:990
get_signal+0x3f2/0x1f70 kernel/signal.c:2588
do_signal+0x8f/0x1670 arch/x86/kernel/signal.c:821
exit_to_usermode_loop+0x204/0x2a0 arch/x86/entry/common.c:163
prepare_exit_to_usermode arch/x86/entry/common.c:198 [inline]
syscall_return_slowpath arch/x86/entry/common.c:271 [inline]
do_syscall_64+0x538/0x620 arch/x86/entry/common.c:296
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x446d39
Code: Bad RIP value.
RSP: 002b:00007ffd5a7d03d8 EFLAGS: 00000246 ORIG_RAX: 000000000000002a
RAX: fffffffffffffffc RBX: 0000000000000003 RCX: 0000000000446d39
RDX: 0000000000000080 RSI: 0000000020000080 RDI: 0000000000000004
RBP: 00007ffd5a7d0410 R08: 0000000000000000 R09: 00000000000000ff
R10: 0000000000000004 R11: 0000000000000246 R12: 0000000000000004
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
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.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches

syzbot

unread,
Jun 21, 2021, 6:24:10 PM6/21/21
to syzkaller...@googlegroups.com
syzbot suspects this issue was fixed by commit:

commit 02f681a5e827f34dc165e1afd341a5897bc535fe
Author: Archie Pusaka <apu...@chromium.org>
Date: Mon Mar 22 06:02:15 2021 +0000

Bluetooth: Set CONF_NOT_COMPLETE as l2cap_chan default

bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10a2ac08300000
start commit: 97a8651c Linux 4.19.189
git tree: linux-4.19.y
kernel config: https://syzkaller.appspot.com/x/.config?x=82311d18bf81a023
dashboard link: https://syzkaller.appspot.com/bug?extid=816b6c4630ff3b31e09d
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11a98f59d00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15fa20c3d00000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: Bluetooth: Set CONF_NOT_COMPLETE as l2cap_chan default

For information about bisection process see: https://goo.gl/tpsmEJ#bisection
Reply all
Reply to author
Forward
0 new messages