WARNING in __queue_work

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 2762b48e Linux 4.14.216
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10c74968d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=e8574522d7c28056
dashboard link: https://syzkaller.appspot.com/bug?extid=6860372995ee310ed930
compiler: gcc (GCC) 10.1.0-syz 20200507

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+686037...@syzkaller.appspotmail.com

XFS (loop4): Invalid superblock magic number
IPVS: ftp: loaded support on port[0] = 21
netlink: 8 bytes leftover after parsing attributes in process `syz-executor.1'.
------------[ cut here ]------------
WARNING: CPU: 1 PID: 11315 at kernel/workqueue.c:1386 __queue_work+0xaaa/0xf70 kernel/workqueue.c:1386
Kernel panic - not syncing: panic_on_warn set ...

CPU: 1 PID: 11315 Comm: syz-executor.2 Not tainted 4.14.216-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: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:__queue_work+0xaaa/0xf70 kernel/workqueue.c:1386
RSP: 0018:ffff88809609f800 EFLAGS: 00010046
RAX: 0000000000040000 RBX: ffff8880a254c300 RCX: ffffc900070f0000
RDX: 0000000000040000 RSI: ffffffff8135e6da RDI: ffff8880a254c324
RBP: 0000000000000008 R08: ffffffff8c090308 R09: 0000000000000001
R10: 0000000000000000 R11: ffff8880a254c300 R12: ffff888067361640
R13: ffff888067361640 R14: 0000000000000000 R15: ffff8880a89f9840
queue_work_on+0x159/0x1d0 kernel/workqueue.c:1490
l2cap_do_send+0x2b2/0x430 net/bluetooth/l2cap_core.c:915
l2cap_chan_send+0x250e/0x37f0 net/bluetooth/l2cap_core.c:2544
l2cap_sock_sendmsg+0x1cd/0x280 net/bluetooth/l2cap_sock.c:975
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:0x45e219
RSP: 002b:00007fecf59c2c68 EFLAGS: 00000246 ORIG_RAX: 0000000000000133
RAX: ffffffffffffffda RBX: 0000000000000004 RCX: 000000000045e219
RDX: 0000000000000500 RSI: 0000000020003f00 RDI: 0000000000000006
RBP: 000000000119bfc8 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000119bf8c
R13: 00007ffeac83f1af R14: 00007fecf59c39c0 R15: 000000000119bf8c
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]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.