syzbot


possible deadlock in process_measurement (3)

Status: upstream: reported C repro on 2021/05/10 12:19
Reported-by: syzbot+ccfcdc8958f74084f16d@syzkaller.appspotmail.com
First crash: 638d, last: 5d16h

Cause bisection: failed (bisect log)
similar bugs (3):
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream possible deadlock in process_measurement (2) C done done 56 794d 1161d 17/24 fixed on 2021/01/06 01:14
linux-4.19 possible deadlock in process_measurement 156 145d 1117d 0/1 auto-obsoleted due to no activity on 2023/01/11 22:20
upstream possible deadlock in process_measurement C 51 1341d 1574d 0/24 closed as invalid on 2019/07/15 16:35
Last patch testing requests:
Created Duration User Patch Repo Result
2021/11/16 14:11 11m phind.uet@gmail.com linux-next report log

Sample crash report:
overlayfs: failed to resolve './bus': -2
======================================================
WARNING: possible circular locking dependency detected
6.1.0-rc7-syzkaller-00159-ga1e9185d20b5 #0 Not tainted
------------------------------------------------------
syz-executor106/9222 is trying to acquire lock:
ffff888027bd3740 (&iint->mutex){+.+.}-{3:3}, at: process_measurement+0x542/0x1b10 security/integrity/ima/ima_main.c:260

but task is already holding lock:
ffff888048256460 (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+0x1a7/0x400 kernel/locking/lockdep.c:5668
       percpu_down_read include/linux/percpu-rwsem.h:51 [inline]
       __sb_start_write include/linux/fs.h:1826 [inline]
       sb_start_write+0x4d/0x1a0 include/linux/fs.h:1901
       mnt_want_write+0x3b/0x80 fs/namespace.c:393
       ovl_maybe_copy_up+0x124/0x190 fs/overlayfs/copy_up.c:1083
       ovl_open+0x106/0x2a0 fs/overlayfs/file.c:152
       do_dentry_open+0x85f/0x11b0 fs/open.c:882
       vfs_open fs/open.c:1013 [inline]
       dentry_open+0xc1/0x120 fs/open.c:1029
       ima_calc_file_hash+0x157/0x1cb0 security/integrity/ima/ima_crypto.c:558
       ima_collect_measurement+0x47f/0x8d0 security/integrity/ima/ima_api.c:292
       process_measurement+0xd60/0x1b10 security/integrity/ima/ima_main.c:337
       ima_file_check+0xe7/0x160 security/integrity/ima/ima_main.c:517
       do_open fs/namei.c:3559 [inline]
       path_openat+0x2654/0x2e00 fs/namei.c:3714
       do_filp_open+0x275/0x500 fs/namei.c:3741
       do_sys_openat2+0x13b/0x500 fs/open.c:1310
       do_sys_open fs/open.c:1326 [inline]
       __do_sys_openat fs/open.c:1342 [inline]
       __se_sys_openat fs/open.c:1337 [inline]
       __x64_sys_openat+0x243/0x290 fs/open.c:1337
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x2b/0x70 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:3097 [inline]
       check_prevs_add kernel/locking/lockdep.c:3216 [inline]
       validate_chain+0x184a/0x6470 kernel/locking/lockdep.c:3831
       __lock_acquire+0x1292/0x1f60 kernel/locking/lockdep.c:5055
       lock_acquire+0x1a7/0x400 kernel/locking/lockdep.c:5668
       __mutex_lock_common+0x1de/0x26c0 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+0x542/0x1b10 security/integrity/ima/ima_main.c:260
       ima_file_check+0xe7/0x160 security/integrity/ima/ima_main.c:517
       do_open fs/namei.c:3559 [inline]
       path_openat+0x2654/0x2e00 fs/namei.c:3714
       do_filp_open+0x275/0x500 fs/namei.c:3741
       do_sys_openat2+0x13b/0x500 fs/open.c:1310
       do_sys_open fs/open.c:1326 [inline]
       __do_sys_open fs/open.c:1334 [inline]
       __se_sys_open fs/open.c:1330 [inline]
       __x64_sys_open+0x221/0x270 fs/open.c:1330
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x2b/0x70 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-executor106/9222:
 #0: ffff888048256460 (sb_writers#4){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:393

stack backtrace:
CPU: 0 PID: 9222 Comm: syz-executor106 Not tainted 6.1.0-rc7-syzkaller-00159-ga1e9185d20b5 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
 check_noncircular+0x2f9/0x3b0 kernel/locking/lockdep.c:2177
 check_prev_add kernel/locking/lockdep.c:3097 [inline]
 check_prevs_add kernel/locking/lockdep.c:3216 [inline]
 validate_chain+0x184a/0x6470 kernel/locking/lockdep.c:3831
 __lock_acquire+0x1292/0x1f60 kernel/locking/lockdep.c:5055
 lock_acquire+0x1a7/0x400 kernel/locking/lockdep.c:5668
 __mutex_lock_common+0x1de/0x26c0 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+0x542/0x1b10 security/integrity/ima/ima_main.c:260
 ima_file_check+0xe7/0x160 security/integrity/ima/ima_main.c:517
 do_open fs/namei.c:3559 [inline]
 path_openat+0x2654/0x2e00 fs/namei.c:3714
 do_filp_open+0x275/0x500 fs/namei.c:3741
 do_sys_openat2+0x13b/0x500 fs/open.c:1310
 do_sys_open fs/open.c:1326 [inline]
 __do_sys_open fs/open.c:1334 [inline]
 __se_sys_open fs/open.c:1330 [inline]
 __x64_sys_open+0x221/0x270 fs/open.c:1330
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x2b/0x70 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f0c8f38a389
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 41 15 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f0c8f31a2f8 EFLAGS: 00000246 ORIG_RAX: 0000000000000002
RAX: ffffffffffffffda RBX: 00007f0c8f4134b0 RCX: 00007f0c8f38a389
RDX: 0000000000000000 RSI: 0000000000080202 RDI: 0000000020000000
RBP: 00007f0c8f3e0088 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0030656c69662f2e
R13: 7269647265707075 R14: 0079616c7265766f R15: 00007f0c8f4134b8
 </TASK>

Fix bisection attempts:
Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets Title
ci-upstream-kasan-gce-smack-root 2021/11/07 14:28 upstream b5013d084e03 064c9eb7 .config console log report syz C
ci-upstream-kasan-gce-smack-root 2021/08/15 20:19 upstream ecf93431963a f115ae98 .config console log report syz C
* Struck through repros no longer work on HEAD.
Crashes (159):
Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets Title
ci-upstream-kasan-gce-smack-root 2022/12/03 22:52 upstream a1e9185d20b5 e080de16 .config console log report syz C [disk image] [vmlinux] [kernel image] possible deadlock in process_measurement
ci-upstream-kasan-gce-root 2022/10/01 14:31 upstream ffb4d94b4314 feb56351 .config console log report syz C [disk image] [vmlinux] possible deadlock in process_measurement
ci2-upstream-fs 2022/09/29 03:20 upstream 49c13ed0316d a41a2080 .config console log report syz C [disk image] [vmlinux] possible deadlock in process_measurement
ci-upstream-kasan-gce-smack-root 2021/09/08 03:32 upstream a2b28235335f 064c9eb7 .config console log report syz C possible deadlock in process_measurement
ci-upstream-kasan-gce-smack-root 2021/09/08 02:39 upstream a2b28235335f 064c9eb7 .config console log report syz C possible deadlock in process_measurement
ci-upstream-kasan-gce-smack-root 2021/07/16 05:27 upstream dd9c7df94c1b f115ae98 .config console log report syz C possible deadlock in process_measurement
ci-upstream-kasan-gce-selinux-root 2021/06/18 14:24 upstream fd0aa1a4567d aba2b2fb .config console log report syz C possible deadlock in process_measurement
ci-upstream-kasan-gce-selinux-root 2021/06/18 12:27 upstream fd0aa1a4567d aba2b2fb .config console log report syz C possible deadlock in process_measurement
ci-upstream-kasan-gce-smack-root 2021/05/16 07:56 upstream c12a29ed9094 f54a5c09 .config console log report syz C possible deadlock in process_measurement
ci-upstream-kasan-gce-smack-root 2021/05/16 06:51 upstream c12a29ed9094 f54a5c09 .config console log report syz C possible deadlock in process_measurement
ci-upstream-kasan-gce-root 2021/05/15 07:27 upstream 25a1298726e9 8bdd5343 .config console log report syz C possible deadlock in process_measurement
ci-upstream-kasan-gce-root 2021/05/15 05:59 upstream 25a1298726e9 8bdd5343 .config console log report syz C possible deadlock in process_measurement
ci-upstream-kasan-gce-root 2021/05/08 15:38 upstream d2b6f8a17919 bc5434be .config console log report syz C possible deadlock in process_measurement
ci-upstream-linux-next-kasan-gce-root 2021/06/09 11:14 linux-next a1f92694393a 5c2fe346 .config console log report syz C possible deadlock in process_measurement
ci-upstream-linux-next-kasan-gce-root 2021/06/09 09:41 linux-next a1f92694393a 5c2fe346 .config console log report syz C possible deadlock in process_measurement
ci-upstream-kasan-gce-smack-root 2022/03/16 15:51 upstream 56e337f2cf13 9e8eaa75 .config console log report syz possible deadlock in process_measurement
ci-upstream-kasan-gce-root 2023/01/31 09:18 upstream 22b8077d0fce 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in process_measurement
ci-qemu-upstream 2023/01/10 15:24 upstream 40c18f363a08 48bc529a .config console log report info possible deadlock in process_measurement
ci-qemu-upstream 2023/01/08 17:09 upstream 93928d485d9d 1dac8c7a .config console log report info possible deadlock in process_measurement
ci-qemu-upstream 2023/01/08 06:29 upstream 9b43a525db12 1dac8c7a .config console log report info possible deadlock in process_measurement
ci-qemu-upstream 2023/01/07 16:13 upstream 0a71553536d2 1dac8c7a .config console log report info possible deadlock in process_measurement
ci2-upstream-fs 2023/01/06 17:31 upstream 41c03ba9beea 1dac8c7a .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in process_measurement
ci-upstream-kasan-gce-smack-root 2023/01/06 01:14 upstream 41c03ba9beea 1dac8c7a .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in process_measurement
ci-qemu-upstream 2023/01/04 06:04 upstream 69b41ac87e4a 1dac8c7a .config console log report info possible deadlock in process_measurement
ci-qemu-upstream 2023/01/03 11:36 upstream 69b41ac87e4a d43e0eb8 .config console log report info possible deadlock in process_measurement
ci-upstream-kasan-gce-root 2023/01/03 01:22 upstream 88603b6dc419 ab32d508 .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in process_measurement
ci-qemu-upstream 2023/01/02 22:09 upstream 88603b6dc419 ab32d508 .config console log report info possible deadlock in process_measurement
ci-qemu-upstream 2022/12/30 04:57 upstream 2258c2dc850b 44712fbc .config console log report info possible deadlock in process_measurement
ci-upstream-kasan-gce-selinux-root 2022/12/29 11:57 upstream 1b929c02afd3 44712fbc .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in process_measurement
ci-upstream-kasan-gce-selinux-root 2022/11/10 14:09 upstream f67dd6ce0723 b2488a87 .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in process_measurement
ci2-upstream-fs 2022/11/07 12:51 upstream f0c4d9fc9cc9 a779b11a .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in process_measurement
ci-upstream-kasan-gce-selinux-root 2022/11/05 21:55 upstream b208b9fbbcba 6d752409 .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in process_measurement
ci-upstream-kasan-gce-root 2022/11/05 10:58 upstream 10d916c86eca 6d752409 .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in process_measurement
ci-upstream-kasan-gce-selinux-root 2022/11/05 04:07 upstream 10d916c86eca 6d752409 .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in process_measurement
ci2-upstream-fs 2022/11/04 22:11 upstream ee6050c8af96 6d752409 .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in process_measurement
ci2-upstream-fs 2022/11/04 11:45 upstream ee6050c8af96 6d752409 .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in process_measurement
ci-upstream-kasan-gce-smack-root 2022/11/04 04:09 upstream f2f32f8af2b0 6d752409 .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in process_measurement
ci2-upstream-fs 2022/11/03 20:57 upstream f2f32f8af2b0 6d752409 .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in process_measurement
ci2-upstream-fs 2022/10/01 06:32 upstream 70575e77839f feb56351 .config console log report info [disk image] [vmlinux] possible deadlock in process_measurement
ci-upstream-kasan-gce-root 2022/09/26 06:26 upstream f76349cf4145 0042f2b4 .config console log report info possible deadlock in process_measurement
ci-upstream-kasan-gce-root 2022/09/25 17:51 upstream 105a36f3694e 0042f2b4 .config console log report info [disk image] [vmlinux] possible deadlock in process_measurement
ci2-upstream-fs 2022/09/25 01:37 upstream 3db61221f4e8 0042f2b4 .config console log report info possible deadlock in process_measurement
ci-upstream-kasan-gce-selinux-root 2022/09/20 05:18 upstream 521a547ced64 dd9a85ff .config console log report info possible deadlock in process_measurement
ci-qemu-upstream 2022/08/13 04:30 upstream c3adefb5baf3 8dfcaa3d .config console log report info possible deadlock in process_measurement
ci-upstream-kasan-gce-root 2021/05/08 12:55 upstream d2b6f8a17919 bc5434be .config console log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/11/05 17:24 upstream b208b9fbbcba 6d752409 .config console log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/09/09 07:35 upstream 506357871c18 f3027468 .config console log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/09/08 12:26 upstream 0066f1b0e275 f3027468 .config console log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/09/08 01:01 upstream 0066f1b0e275 435aeef7 .config console log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/09/07 15:35 upstream 0066f1b0e275 c5b7bc57 .config console log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/09/06 03:16 upstream 53e99dcff61e 9dcd38fc .config console log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/09/02 20:03 upstream 0b3acd1cc022 25194605 .config console log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/09/02 14:26 upstream 42e66b1cc3a0 25194605 .config console log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/09/02 06:27 upstream 42e66b1cc3a0 a805568e .config console log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/08/27 03:01 upstream e022620b5d05 07177916 .config console log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/08/26 06:08 upstream 4c612826bec1 15195ea3 .config console log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/08/25 21:45 upstream 3f5c20055a64 e5fb9cf5 .config console log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/08/25 20:39 upstream 3f5c20055a64 e5fb9cf5 .config console log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/08/25 02:31 upstream c40e8341e3b3 514514f6 .config console log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/08/23 10:53 upstream 072e51356cd5 cea8b0f7 .config console log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/08/23 05:03 upstream 072e51356cd5 26a13b38 .config console log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/08/21 23:40 upstream e3f259d33c0e 26a13b38 .config console log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/08/21 10:36 upstream 15b3f48a4339 26a13b38 .config console log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/08/20 01:18 upstream 50cd95ac4654 26a13b38 .config console log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/08/19 14:47 upstream 4c2d0b039c5c 26a13b38 .config console log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/08/19 01:10 upstream 573ae4f13f63 26a13b38 .config console log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/08/18 10:47 upstream 3b06a2755758 d58e263f .config console log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/08/17 20:08 upstream 274a2eebf80c a9409d47 .config console log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/08/17 12:11 upstream 3cc40a443a04 4e72d229 .config console log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/08/16 21:06 upstream 3cc40a443a04 9e4b39c2 .config console log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/08/15 06:22 upstream 568035b01cfb 8dfcaa3d .config console log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/08/13 10:11 upstream 69dac8e431af 8dfcaa3d .config console log report info possible deadlock in process_measurement
ci-upstream-linux-next-kasan-gce-root 2023/01/04 17:50 linux-next c76083fac3ba 1dac8c7a .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in process_measurement
ci-upstream-linux-next-kasan-gce-root 2022/12/10 13:20 linux-next 591cd61541b9 67be1ae7 .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in process_measurement
ci-upstream-linux-next-kasan-gce-root 2022/11/10 18:21 linux-next 0cdb3579f1ee 3ead01ad .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in process_measurement
ci-upstream-linux-next-kasan-gce-root 2022/11/08 23:49 linux-next 0cdb3579f1ee 060f945e .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in process_measurement
ci-upstream-linux-next-kasan-gce-root 2022/11/08 21:14 linux-next 0cdb3579f1ee 060f945e .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in process_measurement
ci-upstream-linux-next-kasan-gce-root 2022/11/02 22:37 linux-next 61c3426aca2c 08977f5d .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in process_measurement
ci-upstream-linux-next-kasan-gce-root 2022/11/02 16:51 linux-next 61c3426aca2c 08977f5d .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in process_measurement
* Struck through repros no longer work on HEAD.