syzbot


possible deadlock in process_measurement (3)

Status: closed as dup on 2023/06/06 09:59
Labels: overlayfs (incorrect?)
Reported-by: syzbot+ccfcdc8958f74084f16d@syzkaller.appspotmail.com
First crash: 759d, last: 1d15h

Cause bisection: failed (error log, bisect log)
Duplicate of
Title Repro Cause bisect Fix bisect Count Last Reported
possible deadlock in mnt_want_write (2) integrity overlayfs C unreliable 599 3d22h 721d
Discussions (2)
Title Replies (including bot) Last reply
[syzbot] [ext4] Monthly Report 0 (1) 2023/03/24 15:59
[syzbot] possible deadlock in process_measurement (3) 0 (1) 2021/05/10 12:19
Similar bugs (3)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream possible deadlock in process_measurement (2) lsm integrity C done done 56 915d 1282d 17/24 fixed on 2021/01/06 01:14
linux-4.19 possible deadlock in process_measurement 156 265d 1237d 0/1 auto-obsoleted due to no activity on 2023/01/11 22:20
upstream possible deadlock in process_measurement C 51 1462d 1695d 0/24 closed as invalid on 2019/07/15 16:35
Last patch testing requests (1)
Created Duration User Patch Repo Result
2021/11/16 14:11 11m phind.uet@gmail.com linux-next report log
Fix bisection attempts (2)
Created Duration User Patch Repo Result
2021/11/07 14:08 20m bisect fix upstream job log (0) log
2021/08/15 19:59 19m bisect fix upstream job log (0) log

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
6.2.0-rc7-syzkaller-00208-gd12aca5c0cee #0 Not tainted
------------------------------------------------------
syz-executor132/5083 is trying to acquire lock:
ffff8880761c2080 (&iint->mutex){+.+.}-{3:3}, at: process_measurement+0x7a3/0x1c30 security/integrity/ima/ima_main.c:260

but task is already holding lock:
ffff88802adc6460 (sb_writers#4){.+.+}-{0:0}, at: mnt_want_write+0x3f/0x90 fs/namespace.c:508

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (sb_writers#4){.+.+}-{0:0}:
       lock_acquire+0x235/0x630 kernel/locking/lockdep.c:5668
       percpu_down_read include/linux/percpu-rwsem.h:51 [inline]
       __sb_start_write include/linux/fs.h:1814 [inline]
       sb_start_write+0x4d/0x1a0 include/linux/fs.h:1889
       mnt_want_write+0x3f/0x90 fs/namespace.c:508
       ovl_maybe_copy_up+0x115/0x180 fs/overlayfs/copy_up.c:1125
       ovl_open+0x10c/0x2b0 fs/overlayfs/file.c:153
       do_dentry_open+0x7f9/0x10f0 fs/open.c:882
       vfs_open fs/open.c:1013 [inline]
       dentry_open+0xc5/0x120 fs/open.c:1029
       ima_calc_file_hash+0x15d/0x1c00 security/integrity/ima/ima_crypto.c:558
       ima_collect_measurement+0x4cd/0x930 security/integrity/ima/ima_api.c:292
       process_measurement+0xf83/0x1c30 security/integrity/ima/ima_main.c:339
       ima_file_check+0xec/0x170 security/integrity/ima/ima_main.c:519
       do_open fs/namei.c:3559 [inline]
       path_openat+0x265d/0x2e40 fs/namei.c:3714
       do_filp_open+0x234/0x490 fs/namei.c:3741
       do_sys_openat2+0x13f/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+0x225/0x270 fs/open.c:1330
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x41/0xc0 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+0x166b/0x58e0 kernel/locking/lockdep.c:3831
       __lock_acquire+0x125b/0x1f80 kernel/locking/lockdep.c:5055
       lock_acquire+0x235/0x630 kernel/locking/lockdep.c:5668
       __mutex_lock_common+0x1d8/0x2530 kernel/locking/mutex.c:603
       __mutex_lock kernel/locking/mutex.c:747 [inline]
       mutex_lock_nested+0x1b/0x20 kernel/locking/mutex.c:799
       process_measurement+0x7a3/0x1c30 security/integrity/ima/ima_main.c:260
       ima_file_check+0xec/0x170 security/integrity/ima/ima_main.c:519
       do_open fs/namei.c:3559 [inline]
       path_openat+0x265d/0x2e40 fs/namei.c:3714
       do_filp_open+0x234/0x490 fs/namei.c:3741
       do_sys_openat2+0x13f/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+0x225/0x270 fs/open.c:1330
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x41/0xc0 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-executor132/5083:
 #0: ffff88802adc6460 (sb_writers#4){.+.+}-{0:0}, at: mnt_want_write+0x3f/0x90 fs/namespace.c:508

stack backtrace:
CPU: 0 PID: 5083 Comm: syz-executor132 Not tainted 6.2.0-rc7-syzkaller-00208-gd12aca5c0cee #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/21/2023
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e7/0x2d0 lib/dump_stack.c:106
 check_noncircular+0x2fe/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+0x166b/0x58e0 kernel/locking/lockdep.c:3831
 __lock_acquire+0x125b/0x1f80 kernel/locking/lockdep.c:5055
 lock_acquire+0x235/0x630 kernel/locking/lockdep.c:5668
 __mutex_lock_common+0x1d8/0x2530 kernel/locking/mutex.c:603
 __mutex_lock kernel/locking/mutex.c:747 [inline]
 mutex_lock_nested+0x1b/0x20 kernel/locking/mutex.c:799
 process_measurement+0x7a3/0x1c30 security/integrity/ima/ima_main.c:260
 ima_file_check+0xec/0x170 security/integrity/ima/ima_main.c:519
 do_open fs/namei.c:3559 [inline]
 path_openat+0x265d/0x2e40 fs/namei.c:3714
 do_filp_open+0x234/0x490 fs/namei.c:3741
 do_sys_openat2+0x13f/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+0x225/0x270 fs/open.c:1330
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f36c6aaab59
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 11 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 c0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fffed771878 EFLAGS: 00000246 ORIG_RAX: 0000000000000002
RAX: ffffffffffffffda RBX: 0031656c69662f2e RCX: 00007f36c6aaab59
RDX: 0000000000000000 RSI: 000000000014d27e RDI: 0000000020000180
RBP: 0000000000000000 R08: 00007fffed7718a0 R09: 00007fffed7718a0
R10: 00007fffed7718a0 R11: 0000000000000246 R12: 00007fffed77189c
R13: 00007fffed7718d0 R14: 00007fffed7718b0 R15: 0000000000000001
 </TASK>

Crashes (186):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets Manager Title
2023/02/12 07:53 upstream d12aca5c0cee 93e26d60 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs possible deadlock in process_measurement
2022/12/03 22:52 upstream a1e9185d20b5 e080de16 .config console log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in process_measurement
2022/10/01 14:31 upstream ffb4d94b4314 feb56351 .config console log report syz C [disk image] [vmlinux] ci-upstream-kasan-gce-root possible deadlock in process_measurement
2022/09/29 03:20 upstream 49c13ed0316d a41a2080 .config console log report syz C [disk image] [vmlinux] ci2-upstream-fs possible deadlock in process_measurement
2021/09/08 03:32 upstream a2b28235335f 064c9eb7 .config console log report syz C ci-upstream-kasan-gce-smack-root possible deadlock in process_measurement
2021/09/08 02:39 upstream a2b28235335f 064c9eb7 .config console log report syz C ci-upstream-kasan-gce-smack-root possible deadlock in process_measurement
2021/07/16 05:27 upstream dd9c7df94c1b f115ae98 .config console log report syz C ci-upstream-kasan-gce-smack-root possible deadlock in process_measurement
2021/06/18 14:24 upstream fd0aa1a4567d aba2b2fb .config console log report syz C ci-upstream-kasan-gce-selinux-root possible deadlock in process_measurement
2021/06/18 12:27 upstream fd0aa1a4567d aba2b2fb .config console log report syz C ci-upstream-kasan-gce-selinux-root possible deadlock in process_measurement
2021/05/16 07:56 upstream c12a29ed9094 f54a5c09 .config console log report syz C ci-upstream-kasan-gce-smack-root possible deadlock in process_measurement
2021/05/16 06:51 upstream c12a29ed9094 f54a5c09 .config console log report syz C ci-upstream-kasan-gce-smack-root possible deadlock in process_measurement
2021/05/15 07:27 upstream 25a1298726e9 8bdd5343 .config console log report syz C ci-upstream-kasan-gce-root possible deadlock in process_measurement
2021/05/15 05:59 upstream 25a1298726e9 8bdd5343 .config console log report syz C ci-upstream-kasan-gce-root possible deadlock in process_measurement
2021/05/08 15:38 upstream d2b6f8a17919 bc5434be .config console log report syz C ci-upstream-kasan-gce-root possible deadlock in process_measurement
2023/06/02 16:26 linux-next 715abedee4cd a4ae4f42 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-linux-next-kasan-gce-root possible deadlock in process_measurement
2021/06/09 11:14 linux-next a1f92694393a 5c2fe346 .config console log report syz C ci-upstream-linux-next-kasan-gce-root possible deadlock in process_measurement
2021/06/09 09:41 linux-next a1f92694393a 5c2fe346 .config console log report syz C ci-upstream-linux-next-kasan-gce-root possible deadlock in process_measurement
2022/03/16 15:51 upstream 56e337f2cf13 9e8eaa75 .config console log report syz ci-upstream-kasan-gce-smack-root possible deadlock in process_measurement
2023/06/05 05:40 upstream 9561de3a55be a4ae4f42 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in process_measurement
2023/05/11 08:59 upstream d295b66a7b66 0fbd49f4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in process_measurement
2023/05/10 16:42 upstream ad2fd53a7870 0fbd49f4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in process_measurement
2023/05/10 10:13 upstream 16a8829130ca 14b12a99 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in process_measurement
2023/05/08 21:07 upstream ba0ad6ed89fd 90c93c40 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in process_measurement
2023/05/07 12:03 upstream fc4354c6e5c2 90c93c40 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in process_measurement
2023/05/05 17:28 upstream 78b421b6a7c6 4cec9341 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in process_measurement
2023/04/24 00:10 upstream 457391b03803 2b32bd34 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in process_measurement
2023/04/23 21:59 upstream 457391b03803 2b32bd34 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in process_measurement
2023/04/19 15:55 upstream 789b4a41c247 94b4184e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in process_measurement
2023/04/19 05:20 upstream af67688dca57 d931e9f0 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in process_measurement
2023/04/15 01:22 upstream 95abc817ab3a ec410564 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in process_measurement
2023/04/10 04:40 upstream 09a9639e56c0 71147e29 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in process_measurement
2023/04/01 13:32 upstream 7b50567bdcad f325deb0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in process_measurement
2023/03/28 10:53 upstream 3a93e40326c8 47f3aaf1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in process_measurement
2023/03/12 17:36 upstream 134231664868 5205ef30 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in process_measurement
2023/03/04 02:01 upstream 0a3f9a6b0265 f8902b57 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in process_measurement
2023/03/03 13:39 upstream 2eb29d59ddf0 f8902b57 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in process_measurement
2023/03/02 20:18 upstream 04a357b1f6f0 f8902b57 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in process_measurement
2023/01/31 09:18 upstream 22b8077d0fce 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in process_measurement
2023/01/10 15:24 upstream 40c18f363a08 48bc529a .config console log report info ci-qemu-upstream possible deadlock in process_measurement
2023/01/08 17:09 upstream 93928d485d9d 1dac8c7a .config console log report info ci-qemu-upstream possible deadlock in process_measurement
2023/01/08 06:29 upstream 9b43a525db12 1dac8c7a .config console log report info ci-qemu-upstream possible deadlock in process_measurement
2023/01/07 16:13 upstream 0a71553536d2 1dac8c7a .config console log report info ci-qemu-upstream possible deadlock in process_measurement
2023/01/06 17:31 upstream 41c03ba9beea 1dac8c7a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in process_measurement
2023/01/06 01:14 upstream 41c03ba9beea 1dac8c7a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in process_measurement
2023/01/04 06:04 upstream 69b41ac87e4a 1dac8c7a .config console log report info ci-qemu-upstream possible deadlock in process_measurement
2023/01/03 11:36 upstream 69b41ac87e4a d43e0eb8 .config console log report info ci-qemu-upstream possible deadlock in process_measurement
2023/01/03 01:22 upstream 88603b6dc419 ab32d508 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in process_measurement
2023/01/02 22:09 upstream 88603b6dc419 ab32d508 .config console log report info ci-qemu-upstream possible deadlock in process_measurement
2022/12/30 04:57 upstream 2258c2dc850b 44712fbc .config console log report info ci-qemu-upstream possible deadlock in process_measurement
2022/12/29 11:57 upstream 1b929c02afd3 44712fbc .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in process_measurement
2022/11/10 14:09 upstream f67dd6ce0723 b2488a87 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in process_measurement
2022/11/07 12:51 upstream f0c4d9fc9cc9 a779b11a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in process_measurement
2022/11/05 21:55 upstream b208b9fbbcba 6d752409 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in process_measurement
2022/11/05 10:58 upstream 10d916c86eca 6d752409 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in process_measurement
2022/11/05 04:07 upstream 10d916c86eca 6d752409 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in process_measurement
2022/11/04 22:11 upstream ee6050c8af96 6d752409 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in process_measurement
2022/11/04 11:45 upstream ee6050c8af96 6d752409 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in process_measurement
2022/11/04 04:09 upstream f2f32f8af2b0 6d752409 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in process_measurement
2021/05/08 12:55 upstream d2b6f8a17919 bc5434be .config console log report info ci-upstream-kasan-gce-root possible deadlock in process_measurement
2022/11/05 17:24 upstream b208b9fbbcba 6d752409 .config console log report info ci-qemu-upstream-386 possible deadlock in process_measurement
2023/05/23 08:38 linux-next 715abedee4cd 4bce1a3e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in process_measurement
2023/04/25 21:16 linux-next f600e0bbde85 65320f8e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in process_measurement
2023/03/20 16:55 linux-next 73f2c2a7e1d2 7939252e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in process_measurement
2023/03/16 10:29 linux-next 6f72958a49f6 18b58603 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in process_measurement
2023/03/06 11:31 linux-next dc837c1a5137 f8902b57 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in process_measurement
2023/03/06 02:49 linux-next dc837c1a5137 f8902b57 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in process_measurement
2023/01/04 17:50 linux-next c76083fac3ba 1dac8c7a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in process_measurement
2022/12/10 13:20 linux-next 591cd61541b9 67be1ae7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in process_measurement
2022/11/10 18:21 linux-next 0cdb3579f1ee 3ead01ad .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in process_measurement
2022/11/08 23:49 linux-next 0cdb3579f1ee 060f945e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in process_measurement
2022/11/08 21:14 linux-next 0cdb3579f1ee 060f945e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in process_measurement
* Struck through repros no longer work on HEAD.