WARNING in __queue_work (2)

5 views
Skip to first unread message

syzbot

unread,
Dec 7, 2021, 1:42:23 AM12/7/21
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 66722c42ec91 Linux 4.14.256
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15c91badb00000
kernel config: https://syzkaller.appspot.com/x/.config?x=b8004ce84f364d9
dashboard link: https://syzkaller.appspot.com/bug?extid=56ca42a2ea43d5209be1
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)

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

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

PM: Starting manual resume from disk
------------[ cut here ]------------
WARNING: CPU: 0 PID: 9952 at kernel/workqueue.c:1386 __queue_work+0xaaa/0xf70 kernel/workqueue.c:1386
Kernel panic - not syncing: panic_on_warn set ...

CPU: 0 PID: 9952 Comm: syz-executor.1 Not tainted 4.14.256-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/0x281 lib/dump_stack.c:58
panic+0x1f9/0x42d kernel/panic.c:183
__warn.cold+0x20/0x44 kernel/panic.c:547
report_bug+0x208/0x250 lib/bug.c:183
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:__queue_work+0xaaa/0xf70 kernel/workqueue.c:1386
RSP: 0018:ffff88806593f800 EFLAGS: 00010006
RAX: 0000000000040000 RBX: ffff88809e65e140 RCX: ffffc900070c8000
RDX: 00000000000283b0 RSI: ffffffff8135fa4a RDI: ffff88809e65e164
RBP: 0000000000000008 R08: ffffffff8b9d4480 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: ffff888095368dc0
R13: ffff888095368dc0 R14: 0000000000000000 R15: ffff8880a4c88500
queue_work_on+0x159/0x1d0 kernel/workqueue.c:1491
l2cap_do_send+0x2b2/0x430 net/bluetooth/l2cap_core.c:919
l2cap_chan_send+0x2528/0x3800 net/bluetooth/l2cap_core.c:2548
l2cap_sock_sendmsg+0x1cd/0x280 net/bluetooth/l2cap_sock.c:983
sock_sendmsg_nosec net/socket.c:646 [inline]
sock_sendmsg+0xb5/0x100 net/socket.c:656
___sys_sendmsg+0x326/0x800 net/socket.c:2062
__sys_sendmmsg+0x129/0x330 net/socket.c:2152
SYSC_sendmmsg net/socket.c:2183 [inline]
SyS_sendmmsg+0x2f/0x50 net/socket.c:2178
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x7fedcfc58af9
RSP: 002b:00007fedcebce188 EFLAGS: 00000246 ORIG_RAX: 0000000000000133
RAX: ffffffffffffffda RBX: 00007fedcfd6bf60 RCX: 00007fedcfc58af9
RDX: 00000000ffffff1f RSI: 00000000200039c0 RDI: 0000000000000005
RBP: 00007fedcfcb2ff7 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000048048 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffd17db91df R14: 00007fedcebce300 R15: 0000000000022000
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

unread,
Feb 14, 2023, 7:30:39 AM2/14/23
to syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages