syzbot


possible deadlock in flush_workqueue (2)

Status: upstream: reported on 2024/03/13 19:04
Reported-by: syzbot+b38bf7e30aa2b77660c0@syzkaller.appspotmail.com
First crash: 44d, last: 3d18h
Similar bugs (7)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-5.15 possible deadlock in flush_workqueue 1 381d 381d 0/3 auto-obsoleted due to no activity on 2023/08/09 18:38
android-414 possible deadlock in flush_workqueue 1 1629d 1629d 0/1 auto-closed as invalid on 2020/03/10 11:29
upstream possible deadlock in flush_workqueue (2) C done done 256 1582d 2016d 15/26 fixed on 2020/01/31 18:49
linux-4.14 possible deadlock in flush_workqueue C done 15 1622d 1715d 1/1 fixed on 2019/12/18 17:48
linux-4.14 possible deadlock in flush_workqueue (2) 3 1585d 1590d 0/1 auto-closed as invalid on 2020/04/22 20:54
upstream possible deadlock in flush_workqueue net C 73762 2032d 2074d 11/26 fixed on 2018/10/11 14:33
linux-4.19 possible deadlock in flush_workqueue 3 1643d 1654d 0/1 auto-closed as invalid on 2020/02/25 05:02

Sample crash report:
============================================
WARNING: possible recursive locking detected
5.15.156-syzkaller #0 Not tainted
--------------------------------------------
kworker/u5:4/3535 is trying to acquire lock:
ffff8880772ec138 ((wq_completion)hci3){+.+.}-{0:0}, at: flush_workqueue+0x154/0x1610 kernel/workqueue.c:2830

but task is already holding lock:
ffff8880772ec138 ((wq_completion)hci3){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2283

other info that might help us debug this:
 Possible unsafe locking scenario:

       CPU0
       ----
  lock((wq_completion)hci3);
  lock((wq_completion)hci3);

 *** DEADLOCK ***

 May be due to missing lock nesting notation

2 locks held by kworker/u5:4/3535:
 #0: ffff8880772ec138 ((wq_completion)hci3){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2283
 #1: ffffc90002e37d20 ((work_completion)(&hdev->error_reset)){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2285

stack backtrace:
CPU: 1 PID: 3535 Comm: kworker/u5:4 Not tainted 5.15.156-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
Workqueue: hci3 hci_error_reset
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e3/0x2d0 lib/dump_stack.c:106
 print_deadlock_bug kernel/locking/lockdep.c:2946 [inline]
 check_deadlock kernel/locking/lockdep.c:2989 [inline]
 validate_chain+0x46d2/0x5930 kernel/locking/lockdep.c:3775
 __lock_acquire+0x1295/0x1ff0 kernel/locking/lockdep.c:5012
 lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5623
 flush_workqueue+0x170/0x1610 kernel/workqueue.c:2830
 drain_workqueue+0xc5/0x390 kernel/workqueue.c:2995
 destroy_workqueue+0x7b/0xae0 kernel/workqueue.c:4439
 hci_release_dev+0x165/0x1620 net/bluetooth/hci_core.c:4071
 bt_host_release+0x7f/0x90 net/bluetooth/hci_sysfs.c:92
 device_release+0x91/0x1c0
 kobject_cleanup lib/kobject.c:713 [inline]
 kobject_release lib/kobject.c:744 [inline]
 kref_put include/linux/kref.h:65 [inline]
 kobject_put+0x224/0x460 lib/kobject.c:761
 process_one_work+0x8a1/0x10c0 kernel/workqueue.c:2310
 worker_thread+0xaca/0x1280 kernel/workqueue.c:2457
 kthread+0x3f6/0x4f0 kernel/kthread.c:334
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:300
 </TASK>

Crashes (7):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/04/23 09:30 linux-5.15.y c52b9710c83d 21339d7b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in flush_workqueue
2024/04/09 20:13 linux-5.15.y 9465fef4ae35 171ec371 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in flush_workqueue
2024/03/29 22:09 linux-5.15.y 9465fef4ae35 c52bcb23 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in flush_workqueue
2024/03/25 04:53 linux-5.15.y b95c01af2113 0ea90952 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in flush_workqueue
2024/03/13 19:03 linux-5.15.y 574362648507 f919f202 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in flush_workqueue
2024/04/23 22:54 linux-5.15.y c52b9710c83d 21339d7b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in flush_workqueue
2024/03/14 10:41 linux-5.15.y 574362648507 8d8ee116 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in flush_workqueue
* Struck through repros no longer work on HEAD.