[v5.15] WARNING in process_one_work

0 views
Skip to first unread message

syzbot

unread,
Mar 18, 2023, 8:01:00 AM3/18/23
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 8020ae3c051d Linux 5.15.103
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14e39f76c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=d4215fb4040f8f8d
dashboard link: https://syzkaller.appspot.com/bug?extid=5aabb0d46bb2545c5599
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b1c6db1e6932/disk-8020ae3c.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/1285a5761f65/vmlinux-8020ae3c.xz
kernel image: https://storage.googleapis.com/syzbot-assets/e5d44eff1e6b/bzImage-8020ae3c.xz

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

Bluetooth: hci5: command 0x041b tx timeout
------------[ cut here ]------------
WARNING: CPU: 1 PID: 12152 at kernel/workqueue.c:1449 __queue_work+0xc73/0xdc0
Modules linked in:
CPU: 1 PID: 12152 Comm: kworker/1:6 Not tainted 5.15.103-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
Workqueue: events hci_cmd_timeout
RIP: 0010:__queue_work+0xc73/0xdc0 kernel/workqueue.c:1449
Code: 7c 24 10 e8 ff 3c 77 00 e9 bf fc ff ff e8 95 b3 2d 00 89 ee 48 c7 c7 40 df 7c 8c e8 27 f3 db 02 e9 07 fc ff ff e8 7d b3 2d 00 <0f> 0b 48 83 c4 50 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 67 b3 2d 00
RSP: 0018:ffffc9000362faf8 EFLAGS: 00010093
RAX: ffffffff8152c553 RBX: 00000000000b0012 RCX: ffff88801df3ba00
RDX: 0000000000000000 RSI: 0000000000200000 RDI: 0000000000000000
RBP: 0000000000010000 R08: ffffffff8154fd85 R09: ffffed100f6ca167
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffff888020379800 R14: 0000000000000008 R15: 1ffff920006c5f74
FS: 0000000000000000(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f81241479ee CR3: 000000001ffc2000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
queue_work_on+0x14b/0x250 kernel/workqueue.c:1555
process_one_work+0x90d/0x1270 kernel/workqueue.c:2306
worker_thread+0xaca/0x1280 kernel/workqueue.c:2453
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</TASK>


---
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.
Reply all
Reply to author
Forward
0 new messages