syzbot


possible deadlock in process_measurement (5)

Status: upstream: reported on 2025/05/15 13:17
Subsystems: lsm integrity
[Documentation on labels]
Reported-by: syzbot+6529afa25091aee8536c@syzkaller.appspotmail.com
First crash: 38d, last: 2d23h
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [lsm?] [integrity?] possible deadlock in process_measurement (5) 0 (1) 2025/05/15 13:17
Similar bugs (7)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream possible deadlock in process_measurement (4) integrity lsm C done 7976 226d 263d 28/29 fixed on 2024/11/14 10:09
upstream possible deadlock in process_measurement (2) integrity lsm C done done 56 1658d 2025d 15/29 fixed on 2021/01/06 01:14
upstream possible deadlock in process_measurement (3) overlayfs C error 223 593d 1500d 0/29 closed as dup on 2023/06/06 09:59
linux-4.19 possible deadlock in process_measurement 156 1008d 1981d 0/1 auto-obsoleted due to no activity on 2023/01/11 22:20
upstream possible deadlock in process_measurement lsm integrity C 51 2205d 2438d 0/29 closed as invalid on 2019/07/15 16:35
linux-6.1 possible deadlock in process_measurement origin:lts-only C unreliable 1994 1d06h 655d 0/3 upstream: reported C repro on 2023/09/02 00:54
linux-5.15 possible deadlock in process_measurement origin:lts-only C done 4 578d 653d 0/3 auto-obsoleted due to no activity on 2024/10/03 14:31

Sample crash report:
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001
R13: 0000000000000001 R14: 00007f6321db5fa0 R15: 00007ffe22b74df8
 </TASK>
======================================================
WARNING: possible circular locking dependency detected
6.16.0-rc1-syzkaller-00239-g08215f5486ec #0 Not tainted
------------------------------------------------------
syz.3.1033/10895 is trying to acquire lock:
ffff888078bdd5b8 (&ima_iint_mutex_key[depth]){+.+.}-{4:4}, at: process_measurement+0x7e0/0x23e0 security/integrity/ima/ima_main.c:279

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

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #4 (dpm_list_mtx){+.+.}-{4:4}:
       __mutex_lock_common kernel/locking/mutex.c:602 [inline]
       __mutex_lock+0x199/0xb90 kernel/locking/mutex.c:747
       device_pm_add+0x87/0x3e0 drivers/base/power/main.c:138
       device_add+0x9cd/0x1a70 drivers/base/core.c:3655
       device_create_groups_vargs+0x1f8/0x270 drivers/base/core.c:4374
       device_create+0xed/0x130 drivers/base/core.c:4413
       msr_device_create+0x31/0x70 arch/x86/kernel/msr.c:251
       cpuhp_invoke_callback+0x3d5/0xa10 kernel/cpu.c:194
       cpuhp_thread_fun+0x47e/0x6f0 kernel/cpu.c:1104
       smpboot_thread_fn+0x3f7/0xae0 kernel/smpboot.c:164
       kthread+0x3c2/0x780 kernel/kthread.c:464
       ret_from_fork+0x5d4/0x6f0 arch/x86/kernel/process.c:148
       ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245

-> #3 (cpuhp_state-up){+.+.}-{0:0}:
       cpuhp_lock_acquire kernel/cpu.c:103 [inline]
       cpuhp_thread_fun+0x193/0x6f0 kernel/cpu.c:1081
       smpboot_thread_fn+0x3f7/0xae0 kernel/smpboot.c:164
       kthread+0x3c2/0x780 kernel/kthread.c:464
       ret_from_fork+0x5d4/0x6f0 arch/x86/kernel/process.c:148
       ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245

-> #2 (cpu_hotplug_lock){++++}-{0:0}:
       percpu_down_read_internal include/linux/percpu-rwsem.h:53 [inline]
       percpu_down_read include/linux/percpu-rwsem.h:77 [inline]
       cpus_read_lock+0x42/0x160 kernel/cpu.c:490
       class_cpus_read_lock_constructor include/linux/cpuhplock.h:47 [inline]
       ring_buffer_resize+0x105/0x15c0 kernel/trace/ring_buffer.c:2852
       __tracing_resize_ring_buffer.part.0+0x52/0x1f0 kernel/trace/trace.c:6040
       __tracing_resize_ring_buffer kernel/trace/trace.c:6034 [inline]
       tracing_update_buffers+0x102/0x130 kernel/trace/trace.c:6272
       ftrace_event_write+0x14a/0x290 kernel/trace/trace_events.c:1505
       vfs_write+0x2a0/0x1150 fs/read_write.c:684
       ksys_write+0x12a/0x250 fs/read_write.c:738
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0xcd/0x490 arch/x86/entry/syscall_64.c:94
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #1 (trace_types_lock){+.+.}-{4:4}:
       __mutex_lock_common kernel/locking/mutex.c:602 [inline]
       __mutex_lock+0x199/0xb90 kernel/locking/mutex.c:747
       class_mutex_constructor include/linux/mutex.h:225 [inline]
       trace_array_get kernel/trace/trace.c:612 [inline]
       tracing_check_open_get_tr.part.0+0x45/0x130 kernel/trace/trace.c:660
       tracing_check_open_get_tr kernel/trace/trace.c:654 [inline]
       tracing_open_file_tr+0x9a/0x220 kernel/trace/trace.c:4812
       do_dentry_open+0x741/0x1c10 fs/open.c:964
       vfs_open+0x82/0x3f0 fs/open.c:1094
       dentry_open+0x71/0xd0 fs/open.c:1117
       ima_calc_file_hash+0x2b6/0x490 security/integrity/ima/ima_crypto.c:553
       ima_collect_measurement+0x897/0xa40 security/integrity/ima/ima_api.c:293
       process_measurement+0x11fa/0x23e0 security/integrity/ima/ima_main.c:385
       ima_file_check+0xc5/0x110 security/integrity/ima/ima_main.c:613
       security_file_post_open+0x8e/0x210 security/security.c:3130
       do_open fs/namei.c:3889 [inline]
       path_openat+0x1404/0x2cb0 fs/namei.c:4046
       do_filp_open+0x20b/0x470 fs/namei.c:4073
       do_sys_openat2+0x11b/0x1d0 fs/open.c:1437
       do_sys_open fs/open.c:1452 [inline]
       __do_sys_openat fs/open.c:1468 [inline]
       __se_sys_openat fs/open.c:1463 [inline]
       __x64_sys_openat+0x174/0x210 fs/open.c:1463
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0xcd/0x490 arch/x86/entry/syscall_64.c:94
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #0 (&ima_iint_mutex_key[depth]){+.+.}-{4:4}:
       check_prev_add kernel/locking/lockdep.c:3168 [inline]
       check_prevs_add kernel/locking/lockdep.c:3287 [inline]
       validate_chain kernel/locking/lockdep.c:3911 [inline]
       __lock_acquire+0x126f/0x1c90 kernel/locking/lockdep.c:5240
       lock_acquire kernel/locking/lockdep.c:5871 [inline]
       lock_acquire+0x179/0x350 kernel/locking/lockdep.c:5828
       __mutex_lock_common kernel/locking/mutex.c:602 [inline]
       __mutex_lock+0x199/0xb90 kernel/locking/mutex.c:747
       process_measurement+0x7e0/0x23e0 security/integrity/ima/ima_main.c:279
       ima_file_check+0xc5/0x110 security/integrity/ima/ima_main.c:613
       security_file_post_open+0x8e/0x210 security/security.c:3130
       do_open fs/namei.c:3889 [inline]
       path_openat+0x1404/0x2cb0 fs/namei.c:4046
       do_file_open_root+0x322/0x610 fs/namei.c:4098
       file_open_root+0x2a7/0x450 fs/open.c:1416
       kernel_read_file_from_path_initns+0x189/0x260 fs/kernel_read_file.c:163
       fw_get_filesystem_firmware drivers/base/firmware_loader/main.c:549 [inline]
       _request_firmware+0x744/0x1470 drivers/base/firmware_loader/main.c:890
       request_firmware drivers/base/firmware_loader/main.c:966 [inline]
       cache_firmware drivers/base/firmware_loader/main.c:1304 [inline]
       __async_dev_cache_fw_image+0xb1/0x340 drivers/base/firmware_loader/main.c:1418
       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:1474
       dpm_for_each_dev drivers/base/power/main.c:2223 [inline]
       dpm_for_each_dev+0x5a/0xb0 drivers/base/power/main.c:2214
       device_cache_fw_images drivers/base/firmware_loader/main.c:1524 [inline]
       fw_pm_notify+0x81/0x150 drivers/base/firmware_loader/main.c:1575
       notifier_call_chain+0xbc/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:102
       snapshot_open+0x218/0x2b0 kernel/power/user.c:87
       misc_open+0x35d/0x420 drivers/char/misc.c:161
       chrdev_open+0x234/0x6a0 fs/char_dev.c:414
       do_dentry_open+0x741/0x1c10 fs/open.c:964
       vfs_open+0x82/0x3f0 fs/open.c:1094
       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:1437
       do_sys_open fs/open.c:1452 [inline]
       __do_sys_openat fs/open.c:1468 [inline]
       __se_sys_openat fs/open.c:1463 [inline]
       __x64_sys_openat+0x174/0x210 fs/open.c:1463
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0xcd/0x490 arch/x86/entry/syscall_64.c:94
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

other info that might help us debug this:

Chain exists of:
  &ima_iint_mutex_key[depth] --> cpuhp_state-up --> dpm_list_mtx

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(dpm_list_mtx);
                               lock(cpuhp_state-up);
                               lock(dpm_list_mtx);
  lock(&ima_iint_mutex_key[depth]);

 *** DEADLOCK ***

5 locks held by syz.3.1033/10895:
 #0: ffffffff8f303ea8 (misc_mtx){+.+.}-{4:4}, at: misc_open+0x63/0x420 drivers/char/misc.c:125
 #1: ffffffff8e487ba8 (system_transition_mutex){+.+.}-{4:4}, at: lock_system_sleep+0x87/0xa0 kernel/power/main.c:56
 #2: ffffffff8e4c8350 ((pm_chain_head).rwsem){++++}-{4:4}, at: blocking_notifier_call_chain_robust kernel/notifier.c:344 [inline]
 #2: ffffffff8e4c8350 ((pm_chain_head).rwsem){++++}-{4:4}, at: blocking_notifier_call_chain_robust+0xa8/0x160 kernel/notifier.c:333
 #3: ffffffff8f516048 (fw_lock){+.+.}-{4:4}, at: device_cache_fw_images drivers/base/firmware_loader/main.c:1522 [inline]
 #3: ffffffff8f516048 (fw_lock){+.+.}-{4:4}, at: fw_pm_notify+0x69/0x150 drivers/base/firmware_loader/main.c:1575
 #4: ffffffff8f510a48 (dpm_list_mtx){+.+.}-{4:4}, at: device_pm_lock drivers/base/power/main.c:114 [inline]
 #4: ffffffff8f510a48 (dpm_list_mtx){+.+.}-{4:4}, at: dpm_for_each_dev drivers/base/power/main.c:2221 [inline]
 #4: ffffffff8f510a48 (dpm_list_mtx){+.+.}-{4:4}, at: dpm_for_each_dev+0x2d/0xb0 drivers/base/power/main.c:2214

stack backtrace:
CPU: 0 UID: 0 PID: 10895 Comm: syz.3.1033 Not tainted 6.16.0-rc1-syzkaller-00239-g08215f5486ec #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/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:2046
 check_noncircular+0x14c/0x170 kernel/locking/lockdep.c:2178
 check_prev_add kernel/locking/lockdep.c:3168 [inline]
 check_prevs_add kernel/locking/lockdep.c:3287 [inline]
 validate_chain kernel/locking/lockdep.c:3911 [inline]
 __lock_acquire+0x126f/0x1c90 kernel/locking/lockdep.c:5240
 lock_acquire kernel/locking/lockdep.c:5871 [inline]
 lock_acquire+0x179/0x350 kernel/locking/lockdep.c:5828
 __mutex_lock_common kernel/locking/mutex.c:602 [inline]
 __mutex_lock+0x199/0xb90 kernel/locking/mutex.c:747
 process_measurement+0x7e0/0x23e0 security/integrity/ima/ima_main.c:279
 ima_file_check+0xc5/0x110 security/integrity/ima/ima_main.c:613
 security_file_post_open+0x8e/0x210 security/security.c:3130
 do_open fs/namei.c:3889 [inline]
 path_openat+0x1404/0x2cb0 fs/namei.c:4046
 do_file_open_root+0x322/0x610 fs/namei.c:4098
 file_open_root+0x2a7/0x450 fs/open.c:1416
 kernel_read_file_from_path_initns+0x189/0x260 fs/kernel_read_file.c:163
 fw_get_filesystem_firmware drivers/base/firmware_loader/main.c:549 [inline]
 _request_firmware+0x744/0x1470 drivers/base/firmware_loader/main.c:890
 request_firmware drivers/base/firmware_loader/main.c:966 [inline]
 cache_firmware drivers/base/firmware_loader/main.c:1304 [inline]
 __async_dev_cache_fw_image+0xb1/0x340 drivers/base/firmware_loader/main.c:1418
 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:1474
 dpm_for_each_dev drivers/base/power/main.c:2223 [inline]
 dpm_for_each_dev+0x5a/0xb0 drivers/base/power/main.c:2214
 device_cache_fw_images drivers/base/firmware_loader/main.c:1524 [inline]
 fw_pm_notify+0x81/0x150 drivers/base/firmware_loader/main.c:1575
 notifier_call_chain+0xbc/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:102
 snapshot_open+0x218/0x2b0 kernel/power/user.c:87
 misc_open+0x35d/0x420 drivers/char/misc.c:161
 chrdev_open+0x234/0x6a0 fs/char_dev.c:414
 do_dentry_open+0x741/0x1c10 fs/open.c:964
 vfs_open+0x82/0x3f0 fs/open.c:1094
 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:1437
 do_sys_open fs/open.c:1452 [inline]
 __do_sys_openat fs/open.c:1468 [inline]
 __se_sys_openat fs/open.c:1463 [inline]
 __x64_sys_openat+0x174/0x210 fs/open.c:1463
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xcd/0x490 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f6321b8e929
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:00007f6322920038 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007f6321db5fa0 RCX: 00007f6321b8e929
RDX: 0000000000180b01 RSI: 0000200000000000 RDI: ffffffffffffff9c
RBP: 00007f6322920090 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001
R13: 0000000000000001 R14: 00007f6321db5fa0 R15: 00007ffe22b74df8
 </TASK>
(NULL device *): loading /lib/firmware/regulatory.db failed with error -12
(NULL device *): Direct firmware load for regulatory.db failed with error -12
(NULL device *): Falling back to sysfs fallback for: regulatory.db

Crashes (4):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/06/15 22:44 upstream 08215f5486ec 5f4b362d .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto possible deadlock in process_measurement
2025/06/11 06:54 upstream aef17cb3d3c4 5d7e17ca .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto possible deadlock in process_measurement
2025/06/01 20:28 upstream 7d4e49a77d99 3d2f584d .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto possible deadlock in process_measurement
2025/05/11 13:14 upstream 3ce9925823c7 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto possible deadlock in process_measurement
* Struck through repros no longer work on HEAD.