overlayfs: failed to resolve './file0': -2 ====================================================== WARNING: possible circular locking dependency detected 4.19.211-syzkaller #0 Not tainted ------------------------------------------------------ device team3 entered promiscuous mode syz-executor.3/12577 is trying to acquire lock: 0000000033e0e432 (sb_writers#3){.+.+}, at: sb_start_write include/linux/fs.h:1579 [inline] 0000000033e0e432 (sb_writers#3){.+.+}, at: mnt_want_write+0x3a/0xb0 fs/namespace.c:360 but task is already holding lock: 00000000d7b83eba (&iint->mutex){+.+.}, at: process_measurement+0x316/0x1440 security/integrity/ima/ima_main.c:224 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&iint->mutex){+.+.}: process_measurement+0x316/0x1440 security/integrity/ima/ima_main.c:224 ima_file_check+0xb9/0x100 security/integrity/ima/ima_main.c:391 do_last fs/namei.c:3425 [inline] path_openat+0x7e4/0x2df0 fs/namei.c:3537 do_filp_open+0x18c/0x3f0 fs/namei.c:3567 do_sys_open+0x3b3/0x520 fs/open.c:1085 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe -> #0 (sb_writers#3){.+.+}: percpu_down_read_preempt_disable include/linux/percpu-rwsem.h:36 [inline] percpu_down_read include/linux/percpu-rwsem.h:59 [inline] __sb_start_write+0x6e/0x2a0 fs/super.c:1366 sb_start_write include/linux/fs.h:1579 [inline] mnt_want_write+0x3a/0xb0 fs/namespace.c:360 ovl_maybe_copy_up+0x11f/0x190 fs/overlayfs/copy_up.c:888 ovl_open+0xb4/0x260 fs/overlayfs/file.c:126 do_dentry_open+0x4aa/0x1160 fs/open.c:796 vfs_open fs/open.c:902 [inline] dentry_open+0x132/0x1d0 fs/open.c:918 ima_calc_file_hash+0x628/0x8a0 security/integrity/ima/ima_crypto.c:435 ima_collect_measurement+0x4c4/0x570 security/integrity/ima/ima_api.c:231 process_measurement+0xddd/0x1440 security/integrity/ima/ima_main.c:284 ima_file_check+0xb9/0x100 security/integrity/ima/ima_main.c:391 do_last fs/namei.c:3425 [inline] path_openat+0x7e4/0x2df0 fs/namei.c:3537 do_filp_open+0x18c/0x3f0 fs/namei.c:3567 do_sys_open+0x3b3/0x520 fs/open.c:1085 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&iint->mutex); lock(sb_writers#3); lock(&iint->mutex); lock(sb_writers#3); *** DEADLOCK *** 1 lock held by syz-executor.3/12577: #0: 00000000d7b83eba (&iint->mutex){+.+.}, at: process_measurement+0x316/0x1440 security/integrity/ima/ima_main.c:224 stack backtrace: CPU: 1 PID: 12577 Comm: syz-executor.3 Not tainted 4.19.211-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023 Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x1fc/0x2ef lib/dump_stack.c:118 print_circular_bug.constprop.0.cold+0x2d7/0x41e kernel/locking/lockdep.c:1222 check_prev_add kernel/locking/lockdep.c:1866 [inline] check_prevs_add kernel/locking/lockdep.c:1979 [inline] validate_chain kernel/locking/lockdep.c:2420 [inline] __lock_acquire+0x30c9/0x3ff0 kernel/locking/lockdep.c:3416 lock_acquire+0x170/0x3c0 kernel/locking/lockdep.c:3908 percpu_down_read_preempt_disable include/linux/percpu-rwsem.h:36 [inline] percpu_down_read include/linux/percpu-rwsem.h:59 [inline] __sb_start_write+0x6e/0x2a0 fs/super.c:1366 EXT4-fs (loop2): couldn't mount as ext3 due to feature incompatibilities sb_start_write include/linux/fs.h:1579 [inline] mnt_want_write+0x3a/0xb0 fs/namespace.c:360 ovl_maybe_copy_up+0x11f/0x190 fs/overlayfs/copy_up.c:888 ovl_open+0xb4/0x260 fs/overlayfs/file.c:126 do_dentry_open+0x4aa/0x1160 fs/open.c:796 vfs_open fs/open.c:902 [inline] dentry_open+0x132/0x1d0 fs/open.c:918 ima_calc_file_hash+0x628/0x8a0 security/integrity/ima/ima_crypto.c:435 ima_collect_measurement+0x4c4/0x570 security/integrity/ima/ima_api.c:231 process_measurement+0xddd/0x1440 security/integrity/ima/ima_main.c:284 ima_file_check+0xb9/0x100 security/integrity/ima/ima_main.c:391 do_last fs/namei.c:3425 [inline] path_openat+0x7e4/0x2df0 fs/namei.c:3537 do_filp_open+0x18c/0x3f0 fs/namei.c:3567 do_sys_open+0x3b3/0x520 fs/open.c:1085 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe RIP: 0033:0x7fb63a2410f9 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 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:00007fb6387b3168 EFLAGS: 00000246 ORIG_RAX: 0000000000000101 RAX: ffffffffffffffda RBX: 00007fb63a360f80 RCX: 00007fb63a2410f9 RDX: 0000000000000003 RSI: 00000000200001c0 RDI: ffffffffffffff9c RBP: 00007fb63a29cae9 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffec591e70f R14: 00007fb6387b3300 R15: 0000000000022000 hfs: unable to parse mount options EXT4-fs (loop2): couldn't mount as ext3 due to feature incompatibilities overlayfs: upperdir is in-use as upperdir/workdir of another mount, mount with '-o index=off' to override exclusive upperdir protection. overlayfs: failed to resolve './file0': -2 IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready wlan1: Created IBSS using preconfigured BSSID 50:50:50:50:50:50 hfs: unable to parse mount options wlan1: Creating new IBSS network, BSSID 50:50:50:50:50:50 EXT4-fs (loop2): couldn't mount as ext3 due to feature incompatibilities IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready hfs: unable to parse mount options overlayfs: fs on './file0' does not support file handles, falling back to index=off,nfs_export=off. EXT4-fs (loop2): couldn't mount as ext3 due to feature incompatibilities overlayfs: upperdir is in-use as upperdir/workdir of another mount, mount with '-o index=off' to override exclusive upperdir protection. overlayfs: fs on './file0' does not support file handles, falling back to index=off,nfs_export=off. EXT4-fs (loop2): couldn't mount as ext3 due to feature incompatibilities REISERFS (device loop5): found reiserfs format "3.5" with non-standard journal REISERFS (device loop5): using ordered data mode reiserfs: using flush barriers REISERFS (device loop5): journal params: device loop5, size 512, journal first block 18, max trans len 256, max batch 225, max commit age 30, max trans age 30 REISERFS (device loop5): checking transaction log (loop5) REISERFS (device loop5): Using r5 hash to sort names REISERFS (device loop5): using 3.5.x disk format REISERFS (device loop5): Created .reiserfs_priv - reserved for xattr storage. REISERFS (device loop5): found reiserfs format "3.5" with non-standard journal EXT4-fs (loop2): couldn't mount as ext3 due to feature incompatibilities REISERFS (device loop5): using ordered data mode reiserfs: using flush barriers REISERFS (device loop5): journal params: device loop5, size 512, journal first block 18, max trans len 256, max batch 225, max commit age 30, max trans age 30 REISERFS (device loop5): checking transaction log (loop5) REISERFS (device loop5): Using r5 hash to sort names REISERFS (device loop5): using 3.5.x disk format REISERFS (device loop5): Created .reiserfs_priv - reserved for xattr storage. EXT4-fs (loop2): couldn't mount as ext3 due to feature incompatibilities EXT4-fs (loop2): couldn't mount as ext3 due to feature incompatibilities REISERFS (device loop5): found reiserfs format "3.5" with non-standard journal EXT4-fs (loop2): couldn't mount as ext3 due to feature incompatibilities REISERFS (device loop5): using ordered data mode reiserfs: using flush barriers REISERFS (device loop5): journal params: device loop5, size 512, journal first block 18, max trans len 256, max batch 225, max commit age 30, max trans age 30 REISERFS (device loop5): checking transaction log (loop5) REISERFS (device loop5): Using r5 hash to sort names REISERFS (device loop5): using 3.5.x disk format REISERFS (device loop5): Created .reiserfs_priv - reserved for xattr storage. netlink: 'syz-executor.5': attribute type 4 has an invalid length. EXT4-fs (loop2): couldn't mount as ext3 due to feature incompatibilities EXT4-fs (loop2): couldn't mount as ext3 due to feature incompatibilities netlink: 'syz-executor.5': attribute type 4 has an invalid length. EXT4-fs (loop2): couldn't mount as ext3 due to feature incompatibilities netlink: 'syz-executor.5': attribute type 4 has an invalid length. EXT4-fs (loop2): couldn't mount as ext3 due to feature incompatibilities netlink: 'syz-executor.5': attribute type 4 has an invalid length. EXT4-fs (loop2): couldn't mount as ext3 due to feature incompatibilities netlink: 'syz-executor.5': attribute type 4 has an invalid length. EXT4-fs (loop2): couldn't mount as ext3 due to feature incompatibilities EXT4-fs (loop2): couldn't mount as ext3 due to feature incompatibilities netlink: 'syz-executor.5': attribute type 4 has an invalid length. EXT4-fs (loop2): couldn't mount as ext3 due to feature incompatibilities IPVS: ftp: loaded support on port[0] = 21 EXT4-fs (loop2): couldn't mount as ext3 due to feature incompatibilities audit: type=1804 audit(1678039024.412:624): pid=13274 uid=0 auid=4294967295 ses=4294967295 subj==unconfined op=invalid_pcr cause=open_writers comm="syz-executor.4" name="/root/syzkaller-testdir514800512/syzkaller.VdXWxg/876/file0" dev="sda1" ino=15244 res=1 EXT4-fs (loop2): couldn't mount as ext3 due to feature incompatibilities IPVS: ftp: loaded support on port[0] = 21 EXT4-fs (loop2): couldn't mount as ext3 due to feature incompatibilities