possible deadlock in mnt_want

possible deadlock in mnt_want_write (2)
Status: upstream: reported on 2021/06/15 16:59
Reported-by: syzbot+b42fe626038981fb7bfa@syzkaller.appspotmail.com
First crash: 138d, last: 8d22h

similar bugs (4):
Kernel	Title	Repro	Cause bisect	Fix bisect	Count	Last	Reported	Patched	Status
upstream	possible deadlock in mnt_want_write	C	done	done	662	385d	1192d	17/22	fixed on 2020/11/16 12:12
linux-4.19	possible deadlock in mnt_want_write	C			260	6h04m	922d	0/1	upstream: reported C repro on 2019/04/19 16:54
android-49	possible deadlock in mnt_want_write				1	1175d	1175d	0/3	auto-closed as invalid on 2019/02/22 14:57
linux-4.14	possible deadlock in mnt_want_write	C			4516	3d18h	917d	0/1	upstream: reported C repro on 2019/04/25 05:09

Sample crash report:

======================================================
WARNING: possible circular locking dependency detected
5.15.0-rc6-syzkaller #0 Not tainted
------------------------------------------------------
syz-executor.2/28420 is trying to acquire lock:
ffff8881483b4460 (sb_writers#5){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:376

but task is already holding lock:
ffff888024ea4aa0 (&iint->mutex){+.+.}-{3:3}, at: process_measurement+0x7bf/0x1dd0 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+0x19f/0x4d0 kernel/locking/lockdep.c:5625
       __mutex_lock_common+0x1df/0x2550 kernel/locking/mutex.c:596
       __mutex_lock kernel/locking/mutex.c:729 [inline]
       mutex_lock_nested+0x1a/0x20 kernel/locking/mutex.c:743
       process_measurement+0x7bf/0x1dd0 security/integrity/ima/ima_main.c:260
       ima_file_check+0xed/0x170 security/integrity/ima/ima_main.c:516
       do_open fs/namei.c:3430 [inline]
       path_openat+0x2917/0x3670 fs/namei.c:3561
       do_filp_open+0x277/0x4f0 fs/namei.c:3588
       do_sys_openat2+0x13b/0x500 fs/open.c:1200
       do_sys_open fs/open.c:1216 [inline]
       __do_sys_open fs/open.c:1224 [inline]
       __se_sys_open fs/open.c:1220 [inline]
       __x64_sys_open+0x221/0x270 fs/open.c:1220
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x44/0xae

-> #0
 (sb_writers
#5
){.+.+}-{0:0}
:
       check_prev_add kernel/locking/lockdep.c:3051 [inline]
       check_prevs_add kernel/locking/lockdep.c:3174 [inline]
       validate_chain+0x1dfb/0x8240 kernel/locking/lockdep.c:3789
       __lock_acquire+0x1382/0x2b00 kernel/locking/lockdep.c:5015
       lock_acquire+0x19f/0x4d0 kernel/locking/lockdep.c:5625
       percpu_down_read include/linux/percpu-rwsem.h:51 [inline]
       __sb_start_write include/linux/fs.h:1812 [inline]
       sb_start_write+0x4f/0x1a0 include/linux/fs.h:1882
       mnt_want_write+0x3b/0x80 fs/namespace.c:376
       ovl_maybe_copy_up+0x117/0x180 fs/overlayfs/copy_up.c:1047
       ovl_open+0xa2/0x200 fs/overlayfs/file.c:149
       do_dentry_open+0x7cb/0x1020 fs/open.c:822
       vfs_open fs/open.c:945 [inline]
       dentry_open+0xc6/0x120 fs/open.c:961
       ima_calc_file_hash+0x156/0x1b90 security/integrity/ima/ima_crypto.c:557
       ima_collect_measurement+0x27d/0x510 security/integrity/ima/ima_api.c:254
       process_measurement+0x101d/0x1dd0 security/integrity/ima/ima_main.c:337
       ima_file_check+0xed/0x170 security/integrity/ima/ima_main.c:516
       do_open fs/namei.c:3430 [inline]
       path_openat+0x2917/0x3670 fs/namei.c:3561
       do_filp_open+0x277/0x4f0 fs/namei.c:3588
       do_sys_openat2+0x13b/0x500 fs/open.c:1200
       do_sys_open fs/open.c:1216 [inline]
       __do_sys_open fs/open.c:1224 [inline]
       __se_sys_open fs/open.c:1220 [inline]
       __x64_sys_open+0x221/0x270 fs/open.c:1220
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x44/0xae

other info that might help us debug this:

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&iint->mutex);
                               lock(sb_writers#5);
                               lock(&iint->mutex);
  lock(sb_writers#5);

 *** DEADLOCK ***

1 lock held by syz-executor.2/28420:
 #0: ffff888024ea4aa0 (&iint->mutex){+.+.}-{3:3}, at: process_measurement+0x7bf/0x1dd0 security/integrity/ima/ima_main.c:260

stack backtrace:
CPU: 1 PID: 28420 Comm: syz-executor.2 Not tainted 5.15.0-rc6-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1dc/0x2d8 lib/dump_stack.c:106
 check_noncircular+0x2f9/0x3b0 kernel/locking/lockdep.c:2131
 check_prev_add kernel/locking/lockdep.c:3051 [inline]
 check_prevs_add kernel/locking/lockdep.c:3174 [inline]
 validate_chain+0x1dfb/0x8240 kernel/locking/lockdep.c:3789
 __lock_acquire+0x1382/0x2b00 kernel/locking/lockdep.c:5015
 lock_acquire+0x19f/0x4d0 kernel/locking/lockdep.c:5625
 percpu_down_read include/linux/percpu-rwsem.h:51 [inline]
 __sb_start_write include/linux/fs.h:1812 [inline]
 sb_start_write+0x4f/0x1a0 include/linux/fs.h:1882
 mnt_want_write+0x3b/0x80 fs/namespace.c:376
 ovl_maybe_copy_up+0x117/0x180 fs/overlayfs/copy_up.c:1047
 ovl_open+0xa2/0x200 fs/overlayfs/file.c:149
 do_dentry_open+0x7cb/0x1020 fs/open.c:822
 vfs_open fs/open.c:945 [inline]
 dentry_open+0xc6/0x120 fs/open.c:961
 ima_calc_file_hash+0x156/0x1b90 security/integrity/ima/ima_crypto.c:557
 ima_collect_measurement+0x27d/0x510 security/integrity/ima/ima_api.c:254
 process_measurement+0x101d/0x1dd0 security/integrity/ima/ima_main.c:337
 ima_file_check+0xed/0x170 security/integrity/ima/ima_main.c:516
 do_open fs/namei.c:3430 [inline]
 path_openat+0x2917/0x3670 fs/namei.c:3561
 do_filp_open+0x277/0x4f0 fs/namei.c:3588
 do_sys_openat2+0x13b/0x500 fs/open.c:1200
 do_sys_open fs/open.c:1216 [inline]
 __do_sys_open fs/open.c:1224 [inline]
 __se_sys_open fs/open.c:1220 [inline]
 __x64_sys_open+0x221/0x270 fs/open.c:1220
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x44/0xae
RIP: 0033:0x7f8201a97a39
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 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 bc ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f81ff00d188 EFLAGS: 00000246 ORIG_RAX: 0000000000000002
RAX: ffffffffffffffda RBX: 00007f8201b9af60 RCX: 00007f8201a97a39
RDX: 0000000000000000 RSI: 0000000000000003 RDI: 0000000020000000
RBP: 00007f8201af1c5f R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffdb0a10f5f R14: 00007f81ff00d300 R15: 0000000000022000

Crashes (14):
Manager	Time	Kernel	Commit	Syzkaller	Config	Log	Report	VM info	Title
ci-upstream-kasan-gce-smack-root	2021/10/19 14:48	upstream	519d81956ee2	24dc29db	.config	log	report	info	possible deadlock in mnt_want_write
ci-upstream-kasan-gce-smack-root	2021/09/26 09:33	upstream	a5e0aceabef6	8cac236e	.config	log	report	info	possible deadlock in mnt_want_write
ci-upstream-kasan-gce-smack-root	2021/09/08 00:14	upstream	a2b28235335f	064c9eb7	.config	log	report	info	possible deadlock in mnt_want_write
ci-upstream-kasan-gce-smack-root	2021/09/07 22:43	upstream	a2b28235335f	064c9eb7	.config	log	report	info	possible deadlock in mnt_want_write
ci-upstream-kasan-gce-smack-root	2021/09/07 21:54	upstream	a2b28235335f	064c9eb7	.config	log	report	info	possible deadlock in mnt_want_write
ci-upstream-kasan-gce-smack-root	2021/08/29 22:10	upstream	3f5ad13cb012	be2c130d	.config	log	report	info	possible deadlock in mnt_want_write
ci-upstream-kasan-gce-smack-root	2021/07/16 02:19	upstream	dd9c7df94c1b	f115ae98	.config	log	report	info	possible deadlock in mnt_want_write
ci-upstream-kasan-gce-smack-root	2021/07/16 00:58	upstream	dd9c7df94c1b	f115ae98	.config	log	report	info	possible deadlock in mnt_want_write
ci-upstream-kasan-gce-smack-root	2021/07/15 04:40	upstream	8096acd7442e	b9a2f64e	.config	log	report	info	possible deadlock in mnt_want_write
ci-upstream-kasan-gce-smack-root	2021/07/13 16:18	upstream	7fef2edf7cc7	fa0594c3	.config	log	report	info	possible deadlock in mnt_want_write
ci-upstream-kasan-gce-smack-root	2021/07/12 22:27	upstream	7fef2edf7cc7	f415556d	.config	log	report	info	possible deadlock in mnt_want_write
ci-upstream-kasan-gce-smack-root	2021/07/11 20:13	upstream	98f7fdced2e0	8f5a7b8c	.config	log	report	info	possible deadlock in mnt_want_write
ci-upstream-kasan-gce-smack-root	2021/07/07 08:53	upstream	3dbdb38e2869	4846d5c1	.config	log	report	info	possible deadlock in mnt_want_write
ci-upstream-kasan-gce-smack-root	2021/06/11 16:55	upstream	06af8679449d	1ba81399	.config	log	report	info	possible deadlock in mnt_want_write