======================================================
WARNING: possible circular locking dependency detected
4.19.211-syzkaller #0 Not tainted
------------------------------------------------------
syz-executor.0/15043 is trying to acquire lock:
0000000067d82ff8 (&sig->cred_guard_mutex){+.+.}, at: do_io_accounting fs/proc/base.c:2750 [inline]
0000000067d82ff8 (&sig->cred_guard_mutex){+.+.}, at: proc_tid_io_accounting+0x184/0x2b0 fs/proc/base.c:2793

but task is already holding lock:
000000002c76803d (&p->lock){+.+.}, at: seq_read+0x6b/0x11c0 fs/seq_file.c:164

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:1508 [inline]
       __se_sys_sendfile64+0x147/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_rename+0x22b/0x1a50 fs/overlayfs/dir.c:1084
       vfs_rename+0x67e/0x1bc0 fs/namei.c:4479
       do_renameat2+0xb59/0xc70 fs/namei.c:4629
       __do_sys_rename fs/namei.c:4675 [inline]
       __se_sys_rename fs/namei.c:4673 [inline]
       __x64_sys_rename+0x5d/0x80 fs/namei.c:4673
       do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
       entry_SYSCALL_64_after_hwframe+0x49/0xbe

-> #1 (&ovl_i_mutex_dir_key[depth]){++++}:
       inode_lock_shared include/linux/fs.h:758 [inline]
       do_last fs/namei.c:3326 [inline]
       path_openat+0x17ec/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_tid_io_accounting+0x184/0x2b0 fs/proc/base.c:2793
       proc_single_show+0xeb/0x170 fs/proc/base.c:755
       seq_read+0x4e0/0x11c0 fs/seq_file.c:232
       __vfs_read+0xf7/0x750 fs/read_write.c:416
       vfs_read+0x194/0x3c0 fs/read_write.c:452
       ksys_read+0x12b/0x2a0 fs/read_write.c:579
       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 ***

2 locks held by syz-executor.0/15043:
 #0: 00000000dd850f8c (&f->f_pos_lock){+.+.}, at: __fdget_pos+0x26f/0x310 fs/file.c:767
 #1: 000000002c76803d (&p->lock){+.+.}, at: seq_read+0x6b/0x11c0 fs/seq_file.c:164

stack backtrace:
CPU: 1 PID: 15043 Comm: syz-executor.0 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_tid_io_accounting+0x184/0x2b0 fs/proc/base.c:2793
 proc_single_show+0xeb/0x170 fs/proc/base.c:755
 seq_read+0x4e0/0x11c0 fs/seq_file.c:232
 __vfs_read+0xf7/0x750 fs/read_write.c:416
 vfs_read+0x194/0x3c0 fs/read_write.c:452
 ksys_read+0x12b/0x2a0 fs/read_write.c:579
 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
 entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7f87de1b1109
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:00007f87dcb26168 EFLAGS: 00000246 ORIG_RAX: 0000000000000000
RAX: ffffffffffffffda RBX: 00007f87de2c3f60 RCX: 00007f87de1b1109
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000003
RBP: 00007f87de20b05d R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffd59861d2f R14: 00007f87dcb26300 R15: 0000000000022000
x_tables: duplicate underflow at hook 3
x_tables: duplicate underflow at hook 3
x_tables: duplicate underflow at hook 1
x_tables: duplicate underflow at hook 3
x_tables: duplicate underflow at hook 3
x_tables: duplicate underflow at hook 1
x_tables: duplicate underflow at hook 3
x_tables: duplicate underflow at hook 1
x_tables: duplicate underflow at hook 3
F2FS-fs (loop0): Invalid Fs Meta Ino: node(0) meta(0) root(3)
device batadv_slave_0 entered promiscuous mode
F2FS-fs (loop0): Can't find valid F2FS filesystem in 1th superblock
netlink: 8 bytes leftover after parsing attributes in process `syz-executor.3'.
F2FS-fs (loop0): Magic Mismatch, valid(0xf2f52010) - read(0x0)
device batadv_slave_0 left promiscuous mode
F2FS-fs (loop0): Can't find valid F2FS filesystem in 2th superblock
F2FS-fs (loop0): Invalid Fs Meta Ino: node(0) meta(0) root(3)
F2FS-fs (loop0): Can't find valid F2FS filesystem in 1th superblock
F2FS-fs (loop0): Magic Mismatch, valid(0xf2f52010) - read(0x0)
F2FS-fs (loop0): Can't find valid F2FS filesystem in 2th superblock
device batadv_slave_0 entered promiscuous mode
device batadv_slave_0 left promiscuous mode
device batadv_slave_0 entered promiscuous mode
audit: type=1326 audit(1657524668.304:2725): auid=4294967295 uid=0 gid=0 ses=4294967295 subj==unconfined pid=15494 comm="syz-executor.0" exe="/root/syz-executor.0" sig=31 arch=c000003e syscall=202 compat=0 ip=0x7f87de1b1109 code=0x0
device batadv_slave_0 left promiscuous mode
device batadv_slave_0 entered promiscuous mode
device batadv_slave_0 left promiscuous mode
overlayfs: fs on './file0' does not support file handles, falling back to index=off,nfs_export=off.
IPVS: ftp: loaded support on port[0] = 21
EXT4-fs error (device loop1): ext4_fill_super:4450: inode #2: comm syz-executor.1: iget: root inode unallocated
EXT4-fs (loop1): get root inode failed
EXT4-fs (loop1): mount failed
audit: type=1804 audit(1657524670.994:2726): pid=15984 uid=0 auid=4294967295 ses=4294967295 subj==unconfined op=invalid_pcr cause=open_writers comm="syz-executor.0" name="/root/syzkaller-testdir616910585/syzkaller.MXxULd/4402/cgroup.controllers" dev="sda1" ino=14179 res=1
nbd: must specify a device to reconfigure
EXT4-fs error (device loop1): ext4_fill_super:4450: inode #2: comm syz-executor.1: iget: root inode unallocated
EXT4-fs (loop1): get root inode failed
EXT4-fs (loop1): mount failed
EXT4-fs error (device loop1): ext4_fill_super:4450: inode #2: comm syz-executor.1: iget: root inode unallocated
EXT4-fs (loop1): get root inode failed
EXT4-fs (loop1): mount failed
EXT4-fs (loop3): mounted filesystem without journal. Opts: ,errors=continue
caif:caif_disconnect_client(): nothing to disconnect
EXT4-fs error (device loop1): ext4_fill_super:4450: inode #2: comm syz-executor.1: iget: root inode unallocated
can: request_module (can-proto-0) failed.
EXT4-fs (loop3): mounted filesystem without journal. Opts: ,errors=continue
EXT4-fs (loop1): get root inode failed
EXT4-fs (loop1): mount failed
EXT4-fs (loop3): mounted filesystem without journal. Opts: ,errors=continue
caif:caif_disconnect_client(): nothing to disconnect
EXT4-fs (loop3): mounted filesystem without journal. Opts: ,errors=continue
sctp: [Deprecated]: syz-executor.5 (pid 16202) Use of int in maxseg socket option.
Use struct sctp_assoc_value instead
IPVS: ftp: loaded support on port[0] = 21
EXT4-fs error (device loop1): ext4_fill_super:4450: inode #2: comm syz-executor.1: iget: root inode unallocated
EXT4-fs (loop1): get root inode failed
EXT4-fs (loop1): mount failed
nbd: must specify a device to reconfigure