WARNING in process_one_work (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 3f8a27f9e27b Linux 4.19.211
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=171e019d080000
kernel config: https://syzkaller.appspot.com/x/.config?x=9b9277b418617afe
dashboard link: https://syzkaller.appspot.com/bug?extid=482e978f7a7cf8131516
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)

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

Downloadable assets:
disk image: https://storage.googleapis.com/98c0bdb4abb3/disk-3f8a27f9.raw.xz
vmlinux: https://storage.googleapis.com/ea228ff02669/vmlinux-3f8a27f9.xz

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

sock_sendmsg_nosec net/socket.c:651 [inline]
sock_sendmsg+0xc3/0x120 net/socket.c:661
___sys_sendmsg+0x3b3/0x8e0 net/socket.c:2227
------------[ cut here ]------------
WARNING: CPU: 0 PID: 8140 at net/bluetooth/hci_conn.c:404 hci_conn_timeout.cold+0x11/0x18 net/bluetooth/hci_conn.c:404
Kernel panic - not syncing: panic_on_warn set ...

__sys_sendmmsg+0x195/0x470 net/socket.c:2322
__do_sys_sendmmsg net/socket.c:2351 [inline]
__se_sys_sendmmsg net/socket.c:2348 [inline]
__x64_sys_sendmmsg+0x99/0x100 net/socket.c:2348
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7f233b8a5279
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f233a21a168 EFLAGS: 00000246 ORIG_RAX: 0000000000000133
RAX: ffffffffffffffda RBX: 00007f233b9b7f80 RCX: 00007f233b8a5279
RDX: 0400000000000107 RSI: 0000000020008440 RDI: 0000000000000004
RBP: 00007f233a21a1d0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000002
R13: 00007ffe15d7f4af R14: 00007f233a21a300 R15: 0000000000022000
CPU: 0 PID: 8140 Comm: kworker/u5:3 Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/26/2022
Workqueue: hci3 hci_conn_timeout
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1fc/0x2ef lib/dump_stack.c:118
panic+0x26a/0x50e kernel/panic.c:186
__warn.cold+0x20/0x5a kernel/panic.c:541
report_bug+0x262/0x2b0 lib/bug.c:183
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:hci_conn_timeout.cold+0x11/0x18 net/bluetooth/hci_conn.c:404
Code: 53 24 ff e8 c7 e2 4e f9 e8 12 a6 84 f9 48 c7 c7 80 92 5d 89 e8 32 bc 02 00 e8 b1 e2 4e f9 48 c7 c7 e0 99 5d 89 e8 10 14 e0 ff <0f> 0b e9 51 03 25 ff e8 99 e2 4e f9 e8 e4 a5 84 f9 48 c7 c7 c0 af
RSP: 0018:ffff8880ab677d10 EFLAGS: 00010286
RAX: 0000000000000024 RBX: ffff8880968c0aa0 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff814dff01 RDI: ffffed10156cef94
RBP: 00000000ffffffff R08: 0000000000000024 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: ffff8880968c0980
R13: ffff8880ab1bf600 R14: ffff8880b24976c0 R15: ffff888096488800
process_one_work+0x864/0x1570 kernel/workqueue.c:2153
worker_thread+0x64c/0x1130 kernel/workqueue.c:2296
kthread+0x33f/0x460 kernel/kthread.c:259
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415
FAULT_INJECTION: forcing a failure.
name failslab, interval 1, probability 0, space 0, times 0
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.