possible deadlock in dpm_for_each_dev

Status: auto-obsoleted due to no activity on 2026/10/10 09:15
Subsystems: pm
[Documentation on labels]
Reported-by: syzbot+2a03726f1d4eff48b278@syzkaller.appspotmail.com
First crash: 831d, last: 284d
Cause bisection: failed (error log, bisect log)
  
Fix bisection: failed (error log, bisect log)
  
▶ ▼ ✨ AI Jobs (9)
ID Workflow Result Correct Bug Created Started Finished Revision
7b95d70d assessment-security 💥 possible deadlock in dpm_for_each_dev 2026/10/09 03:56 2026/10/09 03:56 2026/10/09 04:25 723be09b
4e61c5ad assessment-security 💥 possible deadlock in dpm_for_each_dev 2026/09/09 03:25 2026/09/09 03:25 2026/09/09 03:52 243b72f1
5e414aa0 assessment-security 💥 possible deadlock in dpm_for_each_dev 2026/08/09 21:39 2026/08/09 21:39 2026/08/09 21:56 5d63f80b
5a97c0a1 assessment-security 💥 possible deadlock in dpm_for_each_dev 2026/07/09 01:02 2026/07/09 01:02 2026/07/09 01:27 93f57954
54f77e49 assessment-security 💥 possible deadlock in dpm_for_each_dev 2026/06/22 02:52 2026/06/22 02:52 2026/06/22 03:21 43bfcdb0
16aed4e0 assessment-security 💥 possible deadlock in dpm_for_each_dev 2026/06/14 02:14 2026/06/14 02:14 2026/06/14 02:39 4f06757f
5f1f9213 assessment-security 💥 possible deadlock in dpm_for_each_dev 2026/06/09 18:06 2026/06/09 18:06 2026/06/09 18:26 c36c07f6
852c77cb assessment-security 💥 possible deadlock in dpm_for_each_dev 2026/06/02 15:10 2026/06/02 15:10 2026/06/02 15:41 62fe1528
3ab44a4a assessment-security 💥 possible deadlock in dpm_for_each_dev 2026/05/25 12:09 2026/05/25 12:09 2026/05/25 12:38 c69befb3
▶ ▼ Discussions (9)
Title Replies (including bot) Last reply
[syzbot] Monthly pm report (Oct 2025) 0 (1) 2025/10/07 07:53
[syzbot] Monthly pm report (Sep 2025) 0 (1) 2025/09/03 21:54
[syzbot] Monthly pm report (Jun 2025) 0 (1) 2025/06/17 07:53
[syzbot] Monthly pm report (Feb 2025) 0 (1) 2025/02/21 09:41
[syzbot] Monthly pm report (Jan 2025) 0 (1) 2025/01/17 15:00
[syzbot] Monthly pm report (Oct 2024) 0 (1) 2024/10/28 08:24
[syzbot] Monthly pm report (Sep 2024) 0 (1) 2024/09/26 12:43
[syzbot] Monthly pm report (Aug 2024) 0 (1) 2024/08/26 13:47
[syzbot] [pm?] [usb?] possible deadlock in dpm_for_each_dev 0 (1) 2024/07/07 17:25
▶ ▼ Last patch testing requests (10)
Created Duration User Patch Repo Result
2026/10/10 08:43 31m retest repro upstream no crash job log log
2026/09/02 01:41 29m retest repro upstream no crash job log log
2026/07/25 20:00 26m retest repro upstream log
2026/06/21 22:53 1h55m retest repro upstream log
2026/05/16 19:25 25m retest repro upstream log
2026/04/11 23:31 58m retest repro upstream report log
2026/04/11 23:29 48m retest repro upstream report log
2026/03/07 17:50 17m retest repro upstream report log
2026/03/07 17:38 24m retest repro upstream report log
2025/12/27 14:19 25m retest repro upstream report log
▶ ▼ Fix bisection attempts (14)
Created Duration User Patch Repo Result
2026/01/31 21:07 4m bisect fix upstream error job log
2026/01/01 15:50 3h53m bisect fix upstream OK (0) job log log
2025/12/02 10:41 5h09m bisect fix upstream OK (0) job log log
2025/11/01 00:28 4h55m bisect fix upstream OK (0) job log log
2025/06/16 18:47 3h21m bisect fix upstream OK (0) job log log
2025/05/17 05:43 1h54m bisect fix upstream OK (0) job log log
2025/04/16 11:40 2h29m bisect fix upstream OK (0) job log log
2025/03/17 09:26 2h13m bisect fix upstream OK (0) job log log
2025/02/15 03:04 3h14m bisect fix upstream OK (0) job log log
2025/01/15 23:17 2h38m bisect fix upstream OK (0) job log log
2024/12/05 03:19 2h23m bisect fix upstream OK (0) job log log
2024/10/21 13:43 3h25m bisect fix upstream OK (0) job log log
2024/09/20 19:11 1h51m bisect fix upstream OK (0) job log log
2024/08/19 04:48 3h12m bisect fix upstream OK (0) job log log

Sample crash report:
EXT4-fs error (device sda1): ext4_lookup:1787: inode #274: comm syz.4.5929: iget: checksum invalid
(NULL device *): loading /lib/firmware/regulatory.db failed with error -74
(NULL device *): Direct firmware load for regulatory.db failed with error -74
(NULL device *): Falling back to sysfs fallback for: regulatory.db
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Tainted: G     U             
------------------------------------------------------
syz.4.5929/14370 is trying to acquire lock:
ffffffff8e475550 (umhelper_sem){++++}-{4:4}, at: usermodehelper_read_trylock+0xa9/0x250 kernel/umh.c:214

but task is already holding lock:
ffffffff8f518668 (dpm_list_mtx){+.+.}-{4:4}, at: device_pm_lock drivers/base/power/main.c:128 [inline]
ffffffff8f518668 (dpm_list_mtx){+.+.}-{4:4}, at: dpm_for_each_dev drivers/base/power/main.c:2290 [inline]
ffffffff8f518668 (dpm_list_mtx){+.+.}-{4:4}, at: dpm_for_each_dev+0x2d/0xb0 drivers/base/power/main.c:2283

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (dpm_list_mtx){+.+.}-{4:4}:
       __mutex_lock_common kernel/locking/mutex.c:598 [inline]
       __mutex_lock+0x193/0x1060 kernel/locking/mutex.c:760
       device_pm_add+0x87/0x3e0 drivers/base/power/main.c:152
       device_add+0x9cd/0x1aa0 drivers/base/core.c:3652
       fw_load_sysfs_fallback drivers/base/firmware_loader/fallback.c:86 [inline]
       fw_load_from_user_helper drivers/base/firmware_loader/fallback.c:162 [inline]
       firmware_fallback_sysfs+0x2ec/0xbe0 drivers/base/firmware_loader/fallback.c:238
       _request_firmware+0xfe9/0x1470 drivers/base/firmware_loader/main.c:906
       request_firmware_work_func+0xea/0x250 drivers/base/firmware_loader/main.c:1159
       process_one_work+0x9cf/0x1b70 kernel/workqueue.c:3236
       process_scheduled_works kernel/workqueue.c:3319 [inline]
       worker_thread+0x6c8/0xf10 kernel/workqueue.c:3400
       kthread+0x3c5/0x780 kernel/kthread.c:463
       ret_from_fork+0x56d/0x730 arch/x86/kernel/process.c:148
       ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245

-> #0 (umhelper_sem){++++}-{4:4}:
       check_prev_add kernel/locking/lockdep.c:3165 [inline]
       check_prevs_add kernel/locking/lockdep.c:3284 [inline]
       validate_chain kernel/locking/lockdep.c:3908 [inline]
       __lock_acquire+0x12a6/0x1ce0 kernel/locking/lockdep.c:5237
       lock_acquire kernel/locking/lockdep.c:5868 [inline]
       lock_acquire+0x179/0x350 kernel/locking/lockdep.c:5825
       down_read+0x9b/0x480 kernel/locking/rwsem.c:1537
       usermodehelper_read_trylock+0xa9/0x250 kernel/umh.c:214
       fw_load_from_user_helper drivers/base/firmware_loader/fallback.c:147 [inline]
       firmware_fallback_sysfs+0x6ba/0xbe0 drivers/base/firmware_loader/fallback.c:238
       _request_firmware+0xfe9/0x1470 drivers/base/firmware_loader/main.c:906
       request_firmware drivers/base/firmware_loader/main.c:957 [inline]
       cache_firmware drivers/base/firmware_loader/main.c:1295 [inline]
       __async_dev_cache_fw_image+0xb1/0x340 drivers/base/firmware_loader/main.c:1409
       async_schedule_node_domain+0xd4/0x120 kernel/async.c:221
       async_schedule_domain include/linux/async.h:72 [inline]
       dev_cache_fw_image+0x38e/0x490 drivers/base/firmware_loader/main.c:1465
       dpm_for_each_dev drivers/base/power/main.c:2292 [inline]
       dpm_for_each_dev+0x5d/0xb0 drivers/base/power/main.c:2283
       device_cache_fw_images drivers/base/firmware_loader/main.c:1515 [inline]
       fw_pm_notify+0x81/0x150 drivers/base/firmware_loader/main.c:1566
       notifier_call_chain+0xb9/0x410 kernel/notifier.c:85
       notifier_call_chain_robust kernel/notifier.c:120 [inline]
       blocking_notifier_call_chain_robust kernel/notifier.c:345 [inline]
       blocking_notifier_call_chain_robust+0xc8/0x160 kernel/notifier.c:333
       pm_notifier_call_chain_robust+0x27/0x60 kernel/power/main.c:103
       snapshot_open+0x218/0x2b0 kernel/power/user.c:87
       misc_open+0x35a/0x420 drivers/char/misc.c:161
       chrdev_open+0x234/0x6a0 fs/char_dev.c:414
       do_dentry_open+0x982/0x1530 fs/open.c:965
       vfs_open+0x82/0x3f0 fs/open.c:1095
       do_open fs/namei.c:3887 [inline]
       path_openat+0x1de4/0x2cb0 fs/namei.c:4046
       do_filp_open+0x20b/0x470 fs/namei.c:4073
       do_sys_openat2+0x11b/0x1d0 fs/open.c:1435
       do_sys_open fs/open.c:1450 [inline]
       __do_sys_openat fs/open.c:1466 [inline]
       __se_sys_openat fs/open.c:1461 [inline]
       __x64_sys_openat+0x174/0x210 fs/open.c:1461
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0xcd/0x4c0 arch/x86/entry/syscall_64.c:94
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

other info that might help us debug this:

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(dpm_list_mtx);
                               lock(umhelper_sem);
                               lock(dpm_list_mtx);
  rlock(umhelper_sem);

 *** DEADLOCK ***

5 locks held by syz.4.5929/14370:
 #0: ffffffff8f3080e8 (misc_mtx){+.+.}-{4:4}, at: misc_open+0x63/0x420 drivers/char/misc.c:125
 #1: ffffffff8e484b88 (system_transition_mutex){+.+.}-{4:4}, at: lock_system_sleep+0x87/0xa0 kernel/power/main.c:57
 #2: ffffffff8e4c4ff0 ((pm_chain_head).rwsem){++++}-{4:4}, at: blocking_notifier_call_chain_robust kernel/notifier.c:344 [inline]
 #2: ffffffff8e4c4ff0 ((pm_chain_head).rwsem){++++}-{4:4}, at: blocking_notifier_call_chain_robust+0xa8/0x160 kernel/notifier.c:333
 #3: ffffffff8f51dc68 (fw_lock){+.+.}-{4:4}, at: device_cache_fw_images drivers/base/firmware_loader/main.c:1513 [inline]
 #3: ffffffff8f51dc68 (fw_lock){+.+.}-{4:4}, at: fw_pm_notify+0x69/0x150 drivers/base/firmware_loader/main.c:1566
 #4: ffffffff8f518668 (dpm_list_mtx){+.+.}-{4:4}, at: device_pm_lock drivers/base/power/main.c:128 [inline]
 #4: ffffffff8f518668 (dpm_list_mtx){+.+.}-{4:4}, at: dpm_for_each_dev drivers/base/power/main.c:2290 [inline]
 #4: ffffffff8f518668 (dpm_list_mtx){+.+.}-{4:4}, at: dpm_for_each_dev+0x2d/0xb0 drivers/base/power/main.c:2283

stack backtrace:
CPU: 0 UID: 0 PID: 14370 Comm: syz.4.5929 Tainted: G     U              syzkaller #0 PREEMPT(full) 
Tainted: [U]=USER
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120
 print_circular_bug+0x275/0x350 kernel/locking/lockdep.c:2043
 check_noncircular+0x14c/0x170 kernel/locking/lockdep.c:2175
 check_prev_add kernel/locking/lockdep.c:3165 [inline]
 check_prevs_add kernel/locking/lockdep.c:3284 [inline]
 validate_chain kernel/locking/lockdep.c:3908 [inline]
 __lock_acquire+0x12a6/0x1ce0 kernel/locking/lockdep.c:5237
 lock_acquire kernel/locking/lockdep.c:5868 [inline]
 lock_acquire+0x179/0x350 kernel/locking/lockdep.c:5825
 down_read+0x9b/0x480 kernel/locking/rwsem.c:1537
 usermodehelper_read_trylock+0xa9/0x250 kernel/umh.c:214
 fw_load_from_user_helper drivers/base/firmware_loader/fallback.c:147 [inline]
 firmware_fallback_sysfs+0x6ba/0xbe0 drivers/base/firmware_loader/fallback.c:238
 _request_firmware+0xfe9/0x1470 drivers/base/firmware_loader/main.c:906
 request_firmware drivers/base/firmware_loader/main.c:957 [inline]
 cache_firmware drivers/base/firmware_loader/main.c:1295 [inline]
 __async_dev_cache_fw_image+0xb1/0x340 drivers/base/firmware_loader/main.c:1409
 async_schedule_node_domain+0xd4/0x120 kernel/async.c:221
 async_schedule_domain include/linux/async.h:72 [inline]
 dev_cache_fw_image+0x38e/0x490 drivers/base/firmware_loader/main.c:1465
 dpm_for_each_dev drivers/base/power/main.c:2292 [inline]
 dpm_for_each_dev+0x5d/0xb0 drivers/base/power/main.c:2283
 device_cache_fw_images drivers/base/firmware_loader/main.c:1515 [inline]
 fw_pm_notify+0x81/0x150 drivers/base/firmware_loader/main.c:1566
 notifier_call_chain+0xb9/0x410 kernel/notifier.c:85
 notifier_call_chain_robust kernel/notifier.c:120 [inline]
 blocking_notifier_call_chain_robust kernel/notifier.c:345 [inline]
 blocking_notifier_call_chain_robust+0xc8/0x160 kernel/notifier.c:333
 pm_notifier_call_chain_robust+0x27/0x60 kernel/power/main.c:103
 snapshot_open+0x218/0x2b0 kernel/power/user.c:87
 misc_open+0x35a/0x420 drivers/char/misc.c:161
 chrdev_open+0x234/0x6a0 fs/char_dev.c:414
 do_dentry_open+0x982/0x1530 fs/open.c:965
 vfs_open+0x82/0x3f0 fs/open.c:1095
 do_open fs/namei.c:3887 [inline]
 path_openat+0x1de4/0x2cb0 fs/namei.c:4046
 do_filp_open+0x20b/0x470 fs/namei.c:4073
 do_sys_openat2+0x11b/0x1d0 fs/open.c:1435
 do_sys_open fs/open.c:1450 [inline]
 __do_sys_openat fs/open.c:1466 [inline]
 __se_sys_openat fs/open.c:1461 [inline]
 __x64_sys_openat+0x174/0x210 fs/open.c:1461
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xcd/0x4c0 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f43d378eec9
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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f43d4569038 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007f43d39e6090 RCX: 00007f43d378eec9
RDX: 0000000000080643 RSI: 0000200000001940 RDI: ffffffffffffff9c
RBP: 00007f43d3811f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f43d39e6128 R14: 00007f43d39e6090 R15: 00007ffcb07240e8
 </TASK>

Crashes (9):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/09/26 07:41 upstream 4ff71af020ae 0abd0691 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto possible deadlock in dpm_for_each_dev
2025/09/13 20:36 upstream 5cd64d4f9268 e2beed91 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto possible deadlock in dpm_for_each_dev
2025/08/31 01:40 upstream c8bc81a52d5a 807a3b61 .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto possible deadlock in dpm_for_each_dev
2025/08/25 02:33 upstream 69fd6b99b8f8 bf27483f .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto possible deadlock in dpm_for_each_dev
2025/08/24 12:02 upstream 8d245acc1e88 bf27483f .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto possible deadlock in dpm_for_each_dev
2025/07/12 16:20 upstream 379f604cc3dc 3cda49cf .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in dpm_for_each_dev
2024/07/19 10:43 upstream 68b59730459e ee4e11c8 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in dpm_for_each_dev
2024/07/03 17:17 upstream e9d22f7a6655 409d975c .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in dpm_for_each_dev
2025/07/26 09:47 upstream 5f33ebd2018c fb8f743d .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in dpm_for_each_dev
* Struck through repros no longer work on HEAD.