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: 516d, last: 5d10h

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 672d 1039d 17/24 fixed on 2021/01/06 01:14
linux-4.19 possible deadlock in process_measurement 156 23d 995d 0/1 upstream: reported on 2020/01/15 21:21
upstream possible deadlock in process_measurement C 51 1219d 1452d 0/24 closed as invalid on 2019/07/15 16:35
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.0.0-rc7-syzkaller-00220-gffb4d94b4314 #0 Not tainted
------------------------------------------------------
syz-executor134/3782 is trying to acquire lock:
ffff888075412980 (&iint->mutex){+.+.}-{3:3}, at: process_measurement+0x3b9/0x18b0 security/integrity/ima/ima_main.c:260

but task is already holding lock:
ffff88807e864460 (sb_writers#4){.+.+}-{0:0}, at: do_open fs/namei.c:3550 [inline]
ffff88807e864460 (sb_writers#4){.+.+}-{0:0}, at: path_openat+0x1b5d/0x28f0 fs/namei.c:3691

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (sb_writers#4){.+.+}-{0:0}:
       percpu_down_read include/linux/percpu-rwsem.h:51 [inline]
       __sb_start_write include/linux/fs.h:1826 [inline]
       sb_start_write include/linux/fs.h:1901 [inline]
       mnt_want_write+0x6c/0x3e0 fs/namespace.c:393
       ovl_maybe_copy_up+0x11f/0x190 fs/overlayfs/copy_up.c:1077
       ovl_open+0xf1/0x2d0 fs/overlayfs/file.c:152
       do_dentry_open+0x4a4/0x13a0 fs/open.c:880
       vfs_open fs/open.c:1016 [inline]
       dentry_open+0x132/0x1d0 fs/open.c:1032
       ima_calc_file_hash+0x2c6/0x4a0 security/integrity/ima/ima_crypto.c:558
       ima_collect_measurement+0x5ca/0x710 security/integrity/ima/ima_api.c:292
       process_measurement+0xd1e/0x18b0 security/integrity/ima/ima_main.c:337
       ima_file_check+0xac/0x100 security/integrity/ima/ima_main.c:517
       do_open fs/namei.c:3559 [inline]
       path_openat+0x1611/0x28f0 fs/namei.c:3691
       do_filp_open+0x1b6/0x400 fs/namei.c:3718
       do_sys_openat2+0x16d/0x4c0 fs/open.c:1313
       do_sys_open fs/open.c:1329 [inline]
       __do_sys_openat fs/open.c:1345 [inline]
       __se_sys_openat fs/open.c:1340 [inline]
       __x64_sys_openat+0x13f/0x1f0 fs/open.c:1340
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x35/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:3095 [inline]
       check_prevs_add kernel/locking/lockdep.c:3214 [inline]
       validate_chain kernel/locking/lockdep.c:3829 [inline]
       __lock_acquire+0x2a43/0x56d0 kernel/locking/lockdep.c:5053
       lock_acquire kernel/locking/lockdep.c:5666 [inline]
       lock_acquire+0x1ab/0x570 kernel/locking/lockdep.c:5631
       __mutex_lock_common kernel/locking/mutex.c:603 [inline]
       __mutex_lock+0x12f/0x1350 kernel/locking/mutex.c:747
       process_measurement+0x3b9/0x18b0 security/integrity/ima/ima_main.c:260
       ima_file_check+0xac/0x100 security/integrity/ima/ima_main.c:517
       do_open fs/namei.c:3559 [inline]
       path_openat+0x1611/0x28f0 fs/namei.c:3691
       do_filp_open+0x1b6/0x400 fs/namei.c:3718
       do_sys_openat2+0x16d/0x4c0 fs/open.c:1313
       do_sys_open fs/open.c:1329 [inline]
       __do_sys_open fs/open.c:1337 [inline]
       __se_sys_open fs/open.c:1333 [inline]
       __x64_sys_open+0x119/0x1c0 fs/open.c:1333
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x35/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-executor134/3782:
 #0: ffff88807e864460 (sb_writers#4){.+.+}-{0:0}, at: do_open fs/namei.c:3550 [inline]
 #0: ffff88807e864460 (sb_writers#4){.+.+}-{0:0}, at: path_openat+0x1b5d/0x28f0 fs/namei.c:3691

stack backtrace:
CPU: 1 PID: 3782 Comm: syz-executor134 Not tainted 6.0.0-rc7-syzkaller-00220-gffb4d94b4314 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106
 check_noncircular+0x25f/0x2e0 kernel/locking/lockdep.c:2175
 check_prev_add kernel/locking/lockdep.c:3095 [inline]
 check_prevs_add kernel/locking/lockdep.c:3214 [inline]
 validate_chain kernel/locking/lockdep.c:3829 [inline]
 __lock_acquire+0x2a43/0x56d0 kernel/locking/lockdep.c:5053
 lock_acquire kernel/locking/lockdep.c:5666 [inline]
 lock_acquire+0x1ab/0x570 kernel/locking/lockdep.c:5631
 __mutex_lock_common kernel/locking/mutex.c:603 [inline]
 __mutex_lock+0x12f/0x1350 kernel/locking/mutex.c:747
 process_measurement+0x3b9/0x18b0 security/integrity/ima/ima_main.c:260
 ima_file_check+0xac/0x100 security/integrity/ima/ima_main.c:517
 do_open fs/namei.c:3559 [inline]
 path_openat+0x1611/0x28f0 fs/namei.c:3691
 do_filp_open+0x1b6/0x400 fs/namei.c:3718
 do_sys_openat2+0x16d/0x4c0 fs/open.c:1313
 do_sys_open fs/open.c:1329 [inline]
 __do_sys_open fs/open.c:1337 [inline]
 __se_sys_open fs/open.c:1333 [inline]
 __x64_sys_open+0x119/0x1c0 fs/open.c:1333
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f045b274259
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 21 19 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:00007f045b1f8208 EFLAGS: 00000246 ORIG_RAX: 0000000000000002
RAX: ffffffffffffffda RBX: 00007f045b2fc258 RCX: 00007f045b274259
RDX: 0000000000000000 RSI: 0000000000080202 RDI: 0000000020000000
RBP: 00007f045b2fc250 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f045b2fc25c
R13: 00007ffcd674d2ff R14: 00007f045b1f8300 R15: 0000000000022000
 </TASK>

Fix bisection attempts:
Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Title
ci-upstream-kasan-gce-smack-root 2021/11/07 14:28 upstream b5013d084e03 064c9eb7 .config log report syz C
ci-upstream-kasan-gce-smack-root 2021/08/15 20:19 upstream ecf93431963a f115ae98 .config log report syz C
* Struck through repros no longer work on HEAD.
Crashes (123):
Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Title
ci-upstream-kasan-gce-root 2022/10/01 14:31 upstream ffb4d94b4314 feb56351 .config log report syz C possible deadlock in process_measurement
ci2-upstream-fs 2022/09/29 03:20 upstream 49c13ed0316d a41a2080 .config log report syz C possible deadlock in process_measurement
ci-upstream-kasan-gce-smack-root 2021/09/08 03:32 upstream a2b28235335f 064c9eb7 .config log report syz C possible deadlock in process_measurement
ci-upstream-kasan-gce-smack-root 2021/09/08 02:39 upstream a2b28235335f 064c9eb7 .config log report syz C possible deadlock in process_measurement
ci-upstream-kasan-gce-smack-root 2021/07/16 05:27 upstream dd9c7df94c1b f115ae98 .config log report syz C possible deadlock in process_measurement
ci-upstream-kasan-gce-selinux-root 2021/06/18 14:24 upstream fd0aa1a4567d aba2b2fb .config log report syz C possible deadlock in process_measurement
ci-upstream-kasan-gce-selinux-root 2021/06/18 12:27 upstream fd0aa1a4567d aba2b2fb .config log report syz C possible deadlock in process_measurement
ci-upstream-kasan-gce-smack-root 2021/05/16 07:56 upstream c12a29ed9094 f54a5c09 .config log report syz C possible deadlock in process_measurement
ci-upstream-kasan-gce-smack-root 2021/05/16 06:51 upstream c12a29ed9094 f54a5c09 .config log report syz C possible deadlock in process_measurement
ci-upstream-kasan-gce-root 2021/05/15 07:27 upstream 25a1298726e9 8bdd5343 .config log report syz C possible deadlock in process_measurement
ci-upstream-kasan-gce-root 2021/05/15 05:59 upstream 25a1298726e9 8bdd5343 .config log report syz C possible deadlock in process_measurement
ci-upstream-kasan-gce-root 2021/05/08 15:38 upstream d2b6f8a17919 bc5434be .config 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 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 log report syz C possible deadlock in process_measurement
ci-upstream-kasan-gce-smack-root 2022/03/16 15:51 upstream 56e337f2cf13 9e8eaa75 .config log report syz possible deadlock in process_measurement
ci2-upstream-fs 2022/10/01 06:32 upstream 70575e77839f feb56351 .config log report info possible deadlock in process_measurement
ci-upstream-kasan-gce-root 2022/09/26 06:26 upstream f76349cf4145 0042f2b4 .config log report info possible deadlock in process_measurement
ci-upstream-kasan-gce-root 2022/09/25 17:51 upstream 105a36f3694e 0042f2b4 .config log report info possible deadlock in process_measurement
ci2-upstream-fs 2022/09/25 01:37 upstream 3db61221f4e8 0042f2b4 .config log report info possible deadlock in process_measurement
ci-upstream-kasan-gce-selinux-root 2022/09/20 05:18 upstream 521a547ced64 dd9a85ff .config log report info possible deadlock in process_measurement
ci-qemu-upstream 2022/08/13 04:30 upstream c3adefb5baf3 8dfcaa3d .config log report info possible deadlock in process_measurement
ci-qemu-upstream 2022/07/30 02:24 upstream e65c6a46df94 fef302b1 .config log report info possible deadlock in process_measurement
ci-qemu-upstream 2022/07/26 03:04 upstream 4a57a8400075 34795c51 .config log report info possible deadlock in process_measurement
ci-qemu-upstream 2022/07/22 17:29 upstream 4a57a8400075 22343af4 .config log report info possible deadlock in process_measurement
ci-qemu-upstream 2022/07/19 13:56 upstream 4a57a8400075 72a3cc0c .config log report info possible deadlock in process_measurement
ci-upstream-kasan-gce-selinux-root 2022/07/17 02:52 upstream c658cabbfd32 95cb00d1 .config log report info possible deadlock in process_measurement
ci-qemu-upstream 2022/07/14 00:41 upstream 4a57a8400075 5d921b08 .config log report info possible deadlock in process_measurement
ci-upstream-kasan-gce-smack-root 2022/07/02 19:49 upstream 089866061428 1434eec0 .config log report info possible deadlock in process_measurement
ci-upstream-kasan-gce-root 2021/05/08 12:55 upstream d2b6f8a17919 bc5434be .config log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/09/09 07:35 upstream 506357871c18 f3027468 .config log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/09/08 12:26 upstream 0066f1b0e275 f3027468 .config log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/09/08 01:01 upstream 0066f1b0e275 435aeef7 .config log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/09/07 15:35 upstream 0066f1b0e275 c5b7bc57 .config log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/09/06 03:16 upstream 53e99dcff61e 9dcd38fc .config log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/09/02 20:03 upstream 0b3acd1cc022 25194605 .config log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/09/02 14:26 upstream 42e66b1cc3a0 25194605 .config log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/09/02 06:27 upstream 42e66b1cc3a0 a805568e .config log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/08/27 03:01 upstream e022620b5d05 07177916 .config log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/08/26 06:08 upstream 4c612826bec1 15195ea3 .config log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/08/25 21:45 upstream 3f5c20055a64 e5fb9cf5 .config log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/08/25 20:39 upstream 3f5c20055a64 e5fb9cf5 .config log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/08/25 02:31 upstream c40e8341e3b3 514514f6 .config log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/08/23 10:53 upstream 072e51356cd5 cea8b0f7 .config log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/08/23 05:03 upstream 072e51356cd5 26a13b38 .config log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/08/21 23:40 upstream e3f259d33c0e 26a13b38 .config log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/08/21 10:36 upstream 15b3f48a4339 26a13b38 .config log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/08/20 01:18 upstream 50cd95ac4654 26a13b38 .config log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/08/19 14:47 upstream 4c2d0b039c5c 26a13b38 .config log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/08/19 01:10 upstream 573ae4f13f63 26a13b38 .config log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/08/18 10:47 upstream 3b06a2755758 d58e263f .config log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/08/17 20:08 upstream 274a2eebf80c a9409d47 .config log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/08/17 12:11 upstream 3cc40a443a04 4e72d229 .config log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/08/16 21:06 upstream 3cc40a443a04 9e4b39c2 .config log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/08/15 06:22 upstream 568035b01cfb 8dfcaa3d .config log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/08/13 10:11 upstream 69dac8e431af 8dfcaa3d .config log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/08/12 08:44 upstream 7ebfc85e2cd7 402cd70d .config log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/08/11 23:16 upstream 7ebfc85e2cd7 21724cb2 .config log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/08/08 21:31 upstream 200e340f2196 da700653 .config log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/08/04 00:30 upstream 200e340f2196 1c9013ac .config log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/08/02 17:23 upstream 7d0d3fa7339e 1c9013ac .config log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/07/27 13:26 upstream 4a57a8400075 da9d0366 .config log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/07/25 13:28 upstream 4a57a8400075 664c519c .config log report info possible deadlock in process_measurement
ci-qemu-upstream-386 2022/07/13 20:53 upstream 4a57a8400075 5d921b08 .config log report info possible deadlock in process_measurement
ci-upstream-linux-next-kasan-gce-root 2022/05/10 02:13 linux-next 38a288f5941e 8b277b8e .config log report info possible deadlock in process_measurement
* Struck through repros no longer work on HEAD.