Date | Name | Commit | Repro | Result |
---|---|---|---|---|
2023/05/15 | upstream (ToT) | f1fcbaa18b28 | C | [report] possible deadlock in mnt_want_write |
syzbot |
sign-in | mailing list | source | docs |
🐞 Open [388] 🐞 Fixed [42] 🐞 Invalid [79] ⬇ Missing Backports [13] 📈 Kernel Health 📈 Bug Lifetimes 📈 Fuzzing 📈 Crashes | 💬 Send us feedback |
Date | Name | Commit | Repro | Result |
---|---|---|---|---|
2023/05/15 | upstream (ToT) | f1fcbaa18b28 | C | [report] possible deadlock in mnt_want_write |
Kernel | Title | Repro | Cause bisect | Fix bisect | Count | Last | Reported | Patched | Status |
---|---|---|---|---|---|---|---|---|---|
linux-5.15 | possible deadlock in mnt_want_write origin:upstream | C | 39 | 9d18h | 193d | 0/3 | upstream: reported C repro on 2023/03/21 10:01 | ||
upstream | possible deadlock in mnt_want_write fs | C | done | done | 662 | 1087d | 1894d | 17/25 | fixed on 2020/11/16 12:12 |
linux-4.19 | possible deadlock in mnt_want_write romfs | C | 730 | 207d | 1624d | 0/1 | upstream: reported C repro on 2019/04/19 16:54 | ||
android-49 | possible deadlock in mnt_want_write | 1 | 1877d | 1877d | 0/3 | auto-closed as invalid on 2019/02/22 14:57 | |||
upstream | possible deadlock in mnt_want_write (2) integrity overlayfs | C | unreliable | 830 | 1d00h | 836d | 0/25 | upstream: reported C repro on 2021/06/15 16:59 | |
linux-4.14 | possible deadlock in mnt_want_write ubifs | C | 10467 | 207d | 1619d | 0/1 | upstream: reported C repro on 2019/04/25 05:09 |
Created | Duration | User | Patch | Repo | Result |
---|---|---|---|---|---|
2023/06/14 11:52 | 41m | bisect fix | linux-6.1.y | job log (0) log |
====================================================== WARNING: possible circular locking dependency detected 6.1.28-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor522/3544 is trying to acquire lock: ffff8880283e2460 (sb_writers#4){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:393 but task is already holding lock: ffff888027578080 (&iint->mutex){+.+.}-{3:3}, at: process_measurement+0x7fe/0x1cf0 security/integrity/ima/ima_main.c:260 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&iint->mutex){+.+.}-{3:3}: lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5669 __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: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+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd -> #0 (sb_writers#4){.+.+}-{0:0}: check_prev_add kernel/locking/lockdep.c:3098 [inline] check_prevs_add kernel/locking/lockdep.c:3217 [inline] validate_chain+0x1667/0x58e0 kernel/locking/lockdep.c:3832 __lock_acquire+0x125b/0x1f80 kernel/locking/lockdep.c:5056 lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5669 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:1087 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: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+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(&iint->mutex); lock(sb_writers#4); lock(&iint->mutex); lock(sb_writers#4); *** DEADLOCK *** 1 lock held by syz-executor522/3544: #0: ffff888027578080 (&iint->mutex){+.+.}-{3:3}, at: process_measurement+0x7fe/0x1cf0 security/integrity/ima/ima_main.c:260 stack backtrace: CPU: 1 PID: 3544 Comm: syz-executor522 Not tainted 6.1.28-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/28/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:2178 check_prev_add kernel/locking/lockdep.c:3098 [inline] check_prevs_add kernel/locking/lockdep.c:3217 [inline] validate_chain+0x1667/0x58e0 kernel/locking/lockdep.c:3832 __lock_acquire+0x125b/0x1f80 kernel/locking/lockdep.c:5056 lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5669 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:1087 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: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+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7f0f0d0c11f9 Code: 28 c3 e8 2a 14 00 00 66 2e 0f 1f 84 00 00 00 00 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 c0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fffaa2671f8 EFLAGS: 00000246 ORIG_RAX: 0000000000000101 RAX: ffffffffffffffda RBX: 0030656c69662f2e RCX: 00007f0f0d0c11f9 RDX: 0000000000000003 RSI: 0000000020000340 RDI: 0000000000000006 RBP: 00007f0f0d0851e0 R08: 0000000000000000 R09:
Time | Kernel | Commit | Syzkaller | Config | Log | Report | Syz repro | C repro | VM info | Assets (help?) | Manager | Title |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2023/05/15 01:29 | linux-6.1.y | bf4ad6fa4e53 | 2b9ba477 | .config | console log | report | syz | C | [disk image] [vmlinux] [kernel image] | ci2-linux-6-1-kasan | possible deadlock in mnt_want_write | |
2023/09/27 05:51 | linux-6.1.y | d23900f974e0 | 0b6a67ac | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-6-1-kasan | possible deadlock in mnt_want_write | ||
2023/09/15 06:00 | linux-6.1.y | 09045dae0d90 | 0b6a67ac | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-6-1-kasan | possible deadlock in mnt_want_write | ||
2023/09/06 19:32 | linux-6.1.y | c2cbfe5f5122 | 72324844 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-6-1-kasan | possible deadlock in mnt_want_write | ||
2023/09/05 07:11 | linux-6.1.y | c2cbfe5f5122 | 0b6286dc | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-6-1-kasan | possible deadlock in mnt_want_write | ||
2023/09/04 21:48 | linux-6.1.y | c2cbfe5f5122 | db3306a6 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-6-1-kasan | possible deadlock in mnt_want_write | ||
2023/09/04 13:28 | linux-6.1.y | c2cbfe5f5122 | db3306a6 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-6-1-kasan | possible deadlock in mnt_want_write | ||
2023/09/04 08:39 | linux-6.1.y | c2cbfe5f5122 | 696ea0d2 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-6-1-kasan | possible deadlock in mnt_want_write | ||
2023/09/04 07:51 | linux-6.1.y | c2cbfe5f5122 | 696ea0d2 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-6-1-kasan | possible deadlock in mnt_want_write | ||
2023/07/21 15:07 | linux-6.1.y | a456e1743881 | 28847498 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-6-1-kasan | possible deadlock in mnt_want_write | ||
2023/07/12 04:16 | linux-6.1.y | 61fd484b2cf6 | 2f19aa4f | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-6-1-kasan | possible deadlock in mnt_want_write | ||
2023/07/09 01:49 | linux-6.1.y | 61fd484b2cf6 | 668cb1fa | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-6-1-kasan | possible deadlock in mnt_want_write | ||
2023/07/05 02:19 | linux-6.1.y | 0f4ac6b4c5f0 | f99c2404 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-6-1-kasan | possible deadlock in mnt_want_write | ||
2023/06/17 08:53 | linux-6.1.y | ca87e77a2ef8 | f3921d4d | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-6-1-kasan | possible deadlock in mnt_want_write | ||
2023/06/17 08:26 | linux-6.1.y | ca87e77a2ef8 | f3921d4d | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-6-1-kasan | possible deadlock in mnt_want_write | ||
2023/06/17 07:40 | linux-6.1.y | ca87e77a2ef8 | f3921d4d | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-6-1-kasan | possible deadlock in mnt_want_write | ||
2023/04/24 07:21 | linux-6.1.y | f17b0ab65d17 | 2b32bd34 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-6-1-kasan | possible deadlock in mnt_want_write | ||
2023/03/28 13:05 | linux-6.1.y | e3a87a10f259 | 47f3aaf1 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-6-1-kasan | possible deadlock in mnt_want_write |