Date | Name | Commit | Repro | Result |
---|---|---|---|---|
2023/09/15 | linux-6.1.y (ToT) | 09045dae0d90 | C | [report] possible deadlock in process_measurement |
2023/09/15 | upstream (ToT) | 9fdfb15a3dbf | C | Didn't crash |
syzbot |
sign-in | mailing list | source | docs |
Date | Name | Commit | Repro | Result |
---|---|---|---|---|
2023/09/15 | linux-6.1.y (ToT) | 09045dae0d90 | C | [report] possible deadlock in process_measurement |
2023/09/15 | upstream (ToT) | 9fdfb15a3dbf | C | Didn't crash |
Kernel | Title | Repro | Cause bisect | Fix bisect | Count | Last | Reported | Patched | Status |
---|---|---|---|---|---|---|---|---|---|
upstream | possible deadlock in process_measurement (4) integrity lsm | C | done | 4976 | now | 16d | 0/28 | upstream: reported C repro on 2024/09/28 07:32 | |
upstream | possible deadlock in process_measurement (2) integrity lsm | C | done | done | 56 | 1411d | 1778d | 15/28 | fixed on 2021/01/06 01:14 |
upstream | possible deadlock in process_measurement (3) overlayfs | C | error | 223 | 347d | 1253d | 0/28 | closed as dup on 2023/06/06 09:59 | |
linux-4.19 | possible deadlock in process_measurement | 156 | 762d | 1734d | 0/1 | auto-obsoleted due to no activity on 2023/01/11 22:20 | |||
upstream | possible deadlock in process_measurement lsm integrity | C | 51 | 1958d | 2191d | 0/28 | closed as invalid on 2019/07/15 16:35 | ||
linux-5.15 | possible deadlock in process_measurement origin:lts-only | C | done | 4 | 331d | 406d | 0/3 | auto-obsoleted due to no activity on 2024/10/03 14:31 |
====================================================== WARNING: possible circular locking dependency detected 6.1.53-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor231/3774 is trying to acquire lock: ffff88807e8f23e0 (&iint->mutex){+.+.}-{3:3}, at: process_measurement+0x7fe/0x1cf0 security/integrity/ima/ima_main.c:260 but task is already holding lock: ffff88814c972460 (sb_writers#4){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:393 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (sb_writers#4){.+.+}-{0:0}: lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5661 percpu_down_read include/linux/percpu-rwsem.h:51 [inline] __sb_start_write include/linux/fs.h:1832 [inline] sb_start_write+0x4d/0x1c0 include/linux/fs.h:1907 mnt_want_write+0x3b/0x80 fs/namespace.c:393 ovl_maybe_copy_up+0x111/0x180 fs/overlayfs/copy_up.c:1089 ovl_open+0x108/0x2a0 fs/overlayfs/file.c:153 do_dentry_open+0x7f9/0x10f0 fs/open.c:882 vfs_open fs/open.c:1013 [inline] dentry_open+0xc1/0x120 fs/open.c:1029 ima_calc_file_hash+0x159/0x1c00 security/integrity/ima/ima_crypto.c:558 ima_collect_measurement+0x4d4/0x970 security/integrity/ima/ima_api.c:292 process_measurement+0x1018/0x1cf0 security/integrity/ima/ima_main.c:337 ima_file_check+0xed/0x170 security/integrity/ima/ima_main.c:520 do_open fs/namei.c:3559 [inline] path_openat+0x2687/0x2e60 fs/namei.c:3714 do_filp_open+0x230/0x480 fs/namei.c:3741 do_sys_openat2+0x13b/0x500 fs/open.c:1318 do_sys_open fs/open.c:1334 [inline] __do_sys_open fs/open.c:1342 [inline] __se_sys_open fs/open.c:1338 [inline] __x64_sys_open+0x221/0x270 fs/open.c:1338 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd -> #0 (&iint->mutex){+.+.}-{3:3}: check_prev_add kernel/locking/lockdep.c:3090 [inline] check_prevs_add kernel/locking/lockdep.c:3209 [inline] validate_chain+0x1667/0x58e0 kernel/locking/lockdep.c:3824 __lock_acquire+0x125b/0x1f80 kernel/locking/lockdep.c:5048 lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5661 __mutex_lock_common+0x1d4/0x2520 kernel/locking/mutex.c:603 __mutex_lock kernel/locking/mutex.c:747 [inline] mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:799 process_measurement+0x7fe/0x1cf0 security/integrity/ima/ima_main.c:260 ima_file_check+0xed/0x170 security/integrity/ima/ima_main.c:520 do_open fs/namei.c:3559 [inline] path_openat+0x2687/0x2e60 fs/namei.c:3714 do_filp_open+0x230/0x480 fs/namei.c:3741 do_sys_openat2+0x13b/0x500 fs/open.c:1318 do_sys_open fs/open.c:1334 [inline] __do_sys_openat fs/open.c:1350 [inline] __se_sys_openat fs/open.c:1345 [inline] __x64_sys_openat+0x243/0x290 fs/open.c:1345 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(sb_writers#4); lock(&iint->mutex); lock(sb_writers#4); lock(&iint->mutex); *** DEADLOCK *** 1 lock held by syz-executor231/3774: #0: ffff88814c972460 (sb_writers#4){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:393 stack backtrace: CPU: 1 PID: 3774 Comm: syz-executor231 Not tainted 6.1.53-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/04/2023 Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106 check_noncircular+0x2fa/0x3b0 kernel/locking/lockdep.c:2170 check_prev_add kernel/locking/lockdep.c:3090 [inline] check_prevs_add kernel/locking/lockdep.c:3209 [inline] validate_chain+0x1667/0x58e0 kernel/locking/lockdep.c:3824 __lock_acquire+0x125b/0x1f80 kernel/locking/lockdep.c:5048 lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5661 __mutex_lock_common+0x1d4/0x2520 kernel/locking/mutex.c:603 __mutex_lock kernel/locking/mutex.c:747 [inline] mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:799 process_measurement+0x7fe/0x1cf0 security/integrity/ima/ima_main.c:260 ima_file_check+0xed/0x170 security/integrity/ima/ima_main.c:520 do_open fs/namei.c:3559 [inline] path_openat+0x2687/0x2e60 fs/namei.c:3714 do_filp_open+0x230/0x480 fs/namei.c:3741 do_sys_openat2+0x13b/0x500 fs/open.c:1318 do_sys_open fs/open.c:1334 [inline] __do_sys_openat fs/open.c:1350 [inline] __se_sys_openat fs/open.c:1345 [inline] __x64_sys_openat+0x243/0x290 fs/open.c:1345 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7ff23630c899 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 a1 1a 00 00 90 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 b0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007ff2362cb218 EFLAGS: 00000246 ORIG_RAX: 0000000000000101 RAX: ffffffffffffffda RBX: 00007ff2363963e8 RCX: 00007ff23630c899 RDX: 000000000000275a RSI: 0000000020000040 RDI: 00000000ffffff9c RBP: 00007ff2363963e0 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 00007ff2363632d4 R13: 0030656c69662f2e R14: 00737570635f6576 R15: 0079616c7265766f </TASK>
Time | Kernel | Commit | Syzkaller | Config | Log | Report | Syz repro | C repro | VM info | Assets (help?) | Manager | Title |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2023/09/15 09:01 | linux-6.1.y | 09045dae0d90 | 0b6a67ac | .config | console log | report | syz | C | [disk image] [vmlinux] [kernel image] | ci2-linux-6-1-kasan | possible deadlock in process_measurement | |
2023/11/18 14:19 | linux-6.1.y | fb2635ac69ab | cb976f63 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-6-1-kasan | possible deadlock in process_measurement | ||
2023/11/14 17:07 | linux-6.1.y | fb2635ac69ab | cb976f63 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-6-1-kasan | possible deadlock in process_measurement | ||
2023/11/10 19:54 | linux-6.1.y | fb2635ac69ab | 45e9b83e | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-6-1-kasan | possible deadlock in process_measurement | ||
2023/11/04 15:36 | linux-6.1.y | 4a61839152cc | 500bfdc4 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-6-1-kasan | possible deadlock in process_measurement | ||
2023/11/04 06:33 | linux-6.1.y | 4a61839152cc | 500bfdc4 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-6-1-kasan | possible deadlock in process_measurement | ||
2023/09/04 07:42 | linux-6.1.y | c2cbfe5f5122 | 696ea0d2 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-6-1-kasan | possible deadlock in process_measurement | ||
2023/09/02 00:54 | linux-6.1.y | a2943d2d9a00 | 696ea0d2 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-6-1-kasan | possible deadlock in process_measurement |