====================================================== WARNING: possible circular locking dependency detected overlayfs: overlapping lowerdir path 4.19.211-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.2/23001 is trying to acquire lock: 00000000d07a0aae (&sig->cred_guard_mutex){+.+.}, at: do_io_accounting fs/proc/base.c:2750 [inline] 00000000d07a0aae (&sig->cred_guard_mutex){+.+.}, at: proc_tgid_io_accounting+0x1cf/0x7f0 fs/proc/base.c:2799 but task is already holding lock: 000000002e3de708 (&p->lock){+.+.}, at: seq_read+0x6b/0x11c0 fs/seq_file.c:164 A link change request failed with some changes committed already. Interface ipvlan1 may have been left with an inconsistent configuration, please check. which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #3 (&p->lock){+.+.}: seq_read+0x6b/0x11c0 fs/seq_file.c:164 proc_reg_read+0x1bd/0x2d0 fs/proc/inode.c:231 do_loop_readv_writev fs/read_write.c:701 [inline] do_loop_readv_writev fs/read_write.c:688 [inline] do_iter_read+0x471/0x630 fs/read_write.c:925 vfs_readv+0xe5/0x150 fs/read_write.c:987 kernel_readv fs/splice.c:362 [inline] default_file_splice_read+0x457/0xa00 fs/splice.c:417 do_splice_to+0x10e/0x160 fs/splice.c:881 splice_direct_to_actor+0x2b9/0x8d0 fs/splice.c:959 do_splice_direct+0x1a7/0x270 fs/splice.c:1068 do_sendfile+0x550/0xc30 fs/read_write.c:1447 __do_sys_sendfile64 fs/read_write.c:1502 [inline] __se_sys_sendfile64+0xc4/0x160 fs/read_write.c:1494 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe -> #2 (sb_writers#3){.+.+}: sb_start_write include/linux/fs.h:1579 [inline] mnt_want_write+0x3a/0xb0 fs/namespace.c:360 ovl_link+0x73/0x2b0 fs/overlayfs/dir.c:676 vfs_link+0x7e6/0xc80 fs/namei.c:4243 do_linkat+0x52a/0x810 fs/namei.c:4311 __do_sys_link fs/namei.c:4340 [inline] __se_sys_link fs/namei.c:4338 [inline] __x64_sys_link+0x5d/0x80 fs/namei.c:4338 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe -> #1 (&ovl_i_mutex_key[depth]){+.+.}: inode_lock include/linux/fs.h:748 [inline] process_measurement+0x926/0x1440 security/integrity/ima/ima_main.c:205 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_open_execat+0x11d/0x5b0 fs/exec.c:853 __do_execve_file+0x1a8b/0x2360 fs/exec.c:1770 do_execveat_common fs/exec.c:1879 [inline] do_execve+0x35/0x50 fs/exec.c:1896 __do_sys_execve fs/exec.c:1977 [inline] __se_sys_execve fs/exec.c:1972 [inline] __x64_sys_execve+0x7c/0xa0 fs/exec.c:1972 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe -> #0 (&sig->cred_guard_mutex){+.+.}: __mutex_lock_common kernel/locking/mutex.c:937 [inline] __mutex_lock+0xd7/0x1190 kernel/locking/mutex.c:1078 do_io_accounting fs/proc/base.c:2750 [inline] proc_tgid_io_accounting+0x1cf/0x7f0 fs/proc/base.c:2799 proc_single_show+0xeb/0x170 fs/proc/base.c:755 seq_read+0x4e0/0x11c0 fs/seq_file.c:232 do_loop_readv_writev fs/read_write.c:701 [inline] do_loop_readv_writev fs/read_write.c:688 [inline] do_iter_read+0x471/0x630 fs/read_write.c:925 vfs_readv+0xe5/0x150 fs/read_write.c:987 do_preadv fs/read_write.c:1071 [inline] __do_sys_preadv fs/read_write.c:1121 [inline] __se_sys_preadv fs/read_write.c:1116 [inline] __x64_sys_preadv+0x22b/0x310 fs/read_write.c:1116 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: Chain exists of: &sig->cred_guard_mutex --> sb_writers#3 --> &p->lock Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&p->lock); lock(sb_writers#3); lock(&p->lock); lock(&sig->cred_guard_mutex); *** DEADLOCK *** 1 lock held by syz-executor.2/23001: #0: 000000002e3de708 (&p->lock){+.+.}, at: seq_read+0x6b/0x11c0 fs/seq_file.c:164 stack backtrace: CPU: 0 PID: 23001 Comm: syz-executor.2 Not tainted 4.19.211-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/29/2022 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 __mutex_lock_common kernel/locking/mutex.c:937 [inline] __mutex_lock+0xd7/0x1190 kernel/locking/mutex.c:1078 do_io_accounting fs/proc/base.c:2750 [inline] proc_tgid_io_accounting+0x1cf/0x7f0 fs/proc/base.c:2799 proc_single_show+0xeb/0x170 fs/proc/base.c:755 seq_read+0x4e0/0x11c0 fs/seq_file.c:232 do_loop_readv_writev fs/read_write.c:701 [inline] do_loop_readv_writev fs/read_write.c:688 [inline] do_iter_read+0x471/0x630 fs/read_write.c:925 vfs_readv+0xe5/0x150 fs/read_write.c:987 do_preadv fs/read_write.c:1071 [inline] __do_sys_preadv fs/read_write.c:1121 [inline] __se_sys_preadv fs/read_write.c:1116 [inline] __x64_sys_preadv+0x22b/0x310 fs/read_write.c:1116 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe RIP: 0033:0x7fb4da8eb209 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 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fb4d9260168 EFLAGS: 00000246 ORIG_RAX: 0000000000000127 RAX: ffffffffffffffda RBX: 00007fb4da9fdf60 RCX: 00007fb4da8eb209 RDX: 0000000000000001 RSI: 0000000020000240 RDI: 0000000000000004 RBP: 00007fb4da945161 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffe4a8fbdff R14: 00007fb4d9260300 R15: 0000000000022000 A link change request failed with some changes committed already. Interface ipvlan1 may have been left with an inconsistent configuration, please check. A link change request failed with some changes committed already. Interface ipvlan1 may have been left with an inconsistent configuration, please check. overlayfs: failed to resolve './file0': -2 A link change request failed with some changes committed already. Interface ipvlan1 may have been left with an inconsistent configuration, please check. A link change request failed with some changes committed already. Interface ipvlan1 may have been left with an inconsistent configuration, please check. A link change request failed with some changes committed already. Interface ipvlan1 may have been left with an inconsistent configuration, please check. overlayfs: overlapping lowerdir path A link change request failed with some changes committed already. Interface ipvlan1 may have been left with an inconsistent configuration, please check. overlayfs: fs on './file0' does not support file handles, falling back to index=off,nfs_export=off. overlayfs: overlapping lowerdir path overlayfs: fs on './file0' does not support file handles, falling back to index=off,nfs_export=off. overlayfs: fs on './file0' does not support file handles, falling back to index=off,nfs_export=off. overlayfs: fs on './file0' does not support file handles, falling back to index=off,nfs_export=off. (syz-executor.5,23278,0):ocfs2_parse_options:1513 ERROR: Invalid heartbeat mount options (syz-executor.5,23278,0):ocfs2_fill_super:1225 ERROR: status = -22 overlayfs: fs on './file0' does not support file handles, falling back to index=off,nfs_export=off. (syz-executor.5,23304,0):ocfs2_parse_options:1513 ERROR: Invalid heartbeat mount options (syz-executor.5,23304,1):ocfs2_fill_super:1225 ERROR: status = -22 overlayfs: fs on './file0' does not support file handles, falling back to index=off,nfs_export=off. (syz-executor.5,23343,0):ocfs2_parse_options:1513 ERROR: Invalid heartbeat mount options (syz-executor.5,23343,0):ocfs2_fill_super:1225 ERROR: status = -22 (syz-executor.5,23365,1):ocfs2_parse_options:1513 ERROR: Invalid heartbeat mount options (syz-executor.5,23365,1):ocfs2_fill_super:1225 ERROR: status = -22 overlayfs: overlapping lowerdir path overlayfs: fs on './file0' does not support file handles, falling back to index=off,nfs_export=off. overlayfs: fs on './file0' does not support file handles, falling back to index=off,nfs_export=off. overlayfs: fs on './file0' does not support file handles, falling back to index=off,nfs_export=off. overlayfs: fs on './file0' does not support file handles, falling back to index=off,nfs_export=off. overlayfs: overlapping lowerdir path overlayfs: fs on './file0' does not support file handles, falling back to index=off,nfs_export=off. overlayfs: fs on './file0' does not support file handles, falling back to index=off,nfs_export=off. overlayfs: fs on './file0' does not support file handles, falling back to index=off,nfs_export=off. overlayfs: fs on './file0' does not support file handles, falling back to index=off,nfs_export=off. overlayfs: fs on './file0' does not support file handles, falling back to index=off,nfs_export=off. overlayfs: overlapping lowerdir path overlayfs: fs on './file0' does not support file handles, falling back to index=off,nfs_export=off. overlayfs: fs on './file0' does not support file handles, falling back to index=off,nfs_export=off. overlayfs: overlapping lowerdir path overlayfs: overlapping lowerdir path overlayfs: fs on './file0' does not support file handles, falling back to index=off,nfs_export=off. overlayfs: fs on './file0' does not support file handles, falling back to index=off,nfs_export=off. overlayfs: overlapping lowerdir path overlayfs: fs on './file0' does not support file handles, falling back to index=off,nfs_export=off. overlayfs: fs on './file0' does not support file handles, falling back to index=off,nfs_export=off. overlayfs: fs on './file0' does not support file handles, falling back to index=off,nfs_export=off. overlayfs: overlapping lowerdir path overlayfs: overlapping lowerdir path overlayfs: fs on './file0' does not support file handles, falling back to index=off,nfs_export=off. overlayfs: overlapping lowerdir path overlayfs: fs on './file0' does not support file handles, falling back to index=off,nfs_export=off. overlayfs: failed to resolve './file0': -2 overlayfs: fs on './file0' does not support file handles, falling back to index=off,nfs_export=off. overlayfs: fs on './file0' does not support file handles, falling back to index=off,nfs_export=off. overlayfs: fs on './file0' does not support file handles, falling back to index=off,nfs_export=off. overlayfs: overlapping lowerdir path