====================================================== WARNING: possible circular locking dependency detected 4.19.211-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.1/29372 is trying to acquire lock: 00000000d9411d68 (&sig->cred_guard_mutex){+.+.}, at: do_io_accounting fs/proc/base.c:2750 [inline] 00000000d9411d68 (&sig->cred_guard_mutex){+.+.}, at: proc_tid_io_accounting+0x184/0x2b0 fs/proc/base.c:2793 but task is already holding lock: 00000000c50576b1 (&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: -> #4 (&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 -> #3 (sb_writers#3){.+.+}: sb_start_write include/linux/fs.h:1579 [inline] mnt_want_write+0x3a/0xb0 fs/namespace.c:360 ovl_create_object+0x96/0x290 fs/overlayfs/dir.c:602 lookup_open+0x893/0x1a20 fs/namei.c:3235 do_last fs/namei.c:3327 [inline] path_openat+0x1094/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 -> #2 (&ovl_i_mutex_dir_key[depth]#2){++++}: inode_lock_shared include/linux/fs.h:758 [inline] lookup_slow fs/namei.c:1688 [inline] lookup_one_len_unlocked+0x111/0x140 fs/namei.c:2573 ovl_lookup_single+0x60/0x920 fs/overlayfs/namei.c:206 ovl_lookup_layer+0x3bd/0x440 fs/overlayfs/namei.c:292 ovl_lookup+0x729/0x1a00 fs/overlayfs/namei.c:903 __lookup_slow+0x246/0x4a0 fs/namei.c:1672 lookup_slow fs/namei.c:1689 [inline] walk_component+0x7ac/0xda0 fs/namei.c:1811 link_path_walk.part.0+0x901/0x1230 fs/namei.c:2142 link_path_walk fs/namei.c:2073 [inline] path_parentat+0x51/0x140 fs/namei.c:2367 filename_parentat+0x198/0x590 fs/namei.c:2389 do_renameat2+0x193/0xc70 fs/namei.c:4547 __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 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.1/29372: #0: 00000000c50576b1 (&p->lock){+.+.}, at: seq_read+0x6b/0x11c0 fs/seq_file.c:164 stack backtrace: CPU: 1 PID: 29372 Comm: syz-executor.1 Not tainted 4.19.211-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 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 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:0x7fb960ce40e9 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:00007fb95f659168 EFLAGS: 00000246 ORIG_RAX: 0000000000000127 RAX: ffffffffffffffda RBX: 00007fb960df6f60 RCX: 00007fb960ce40e9 RDX: 0000000000000001 RSI: 0000000020000280 RDI: 0000000000000003 RBP: 00007fb960d3e08d R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007fffe10180cf R14: 00007fb95f659300 R15: 0000000000022000 Bluetooth: hci1: command 0x0419 tx timeout EXT4-fs (loop4): Ignoring removed bh option overlayfs: fs on './file0' does not support file handles, falling back to index=off,nfs_export=off. EXT4-fs (loop4): bad geometry: block count 767 exceeds size of device (527 blocks) IPVS: ftp: loaded support on port[0] = 21 EXT4-fs (loop4): Ignoring removed bh option EXT4-fs (loop4): bad geometry: block count 767 exceeds size of device (527 blocks) EXT4-fs (loop4): Ignoring removed bh option EXT4-fs (loop4): bad geometry: block count 767 exceeds size of device (527 blocks) overlayfs: failed to resolve './file1': -2 EXT4-fs (loop4): Ignoring removed bh option EXT4-fs (loop4): bad geometry: block count 767 exceeds size of device (527 blocks) 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 (loop4): Ignoring removed bh option EXT4-fs (loop4): bad geometry: block count 767 exceeds size of device (527 blocks) overlayfs: fs on './file0' does not support file handles, falling back to index=off,nfs_export=off. EXT4-fs (loop4): Ignoring removed bh option EXT4-fs (loop4): bad geometry: block count 767 exceeds size of device (527 blocks) 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 (loop4): Ignoring removed bh option EXT4-fs (loop4): bad geometry: block count 767 exceeds size of device (527 blocks) EXT4-fs (loop4): Ignoring removed bh option EXT4-fs (loop4): ext4_check_descriptors: Inode bitmap for group 0 not in group (block 4)! EXT4-fs (loop4): group descriptors corrupted! overlayfs: fs on './file0' does not support file handles, falling back to index=off,nfs_export=off. EXT4-fs (loop4): Ignoring removed bh option IPVS: ftp: loaded support on port[0] = 21 EXT4-fs (loop4): ext4_check_descriptors: Inode table for group 0 not in group (block 5)! EXT4-fs (loop4): group descriptors corrupted! overlayfs: fs on './file0' does not support file handles, falling back to index=off,nfs_export=off. EXT4-fs (loop4): Ignoring removed bh option overlayfs: fs on './file0' does not support file handles, falling back to index=off,nfs_export=off. EXT4-fs (loop4): ext4_check_descriptors: Checksum for group 0 failed (60935!=0) IPVS: ftp: loaded support on port[0] = 21 IPVS: ftp: loaded support on port[0] = 21 EXT4-fs (loop4): orphan cleanup on readonly fs EXT4-fs error (device loop4): ext4_quota_enable:5844: comm syz-executor.4: inode #237: comm syz-executor.4: iget: illegal inode # EXT4-fs error (device loop4): ext4_quota_enable:5846: comm syz-executor.4: Bad quota inode # 237 EXT4-fs warning (device loop4): ext4_enable_quotas:5883: Failed to enable quota tracking (type=0, err=-117). Please run e2fsck to fix. EXT4-fs (loop4): Cannot turn on quotas: error -117 EXT4-fs (loop4): mounted filesystem without journal. Opts: norecovery,auto_da_alloc,bh,,errors=continue 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 (loop4): Ignoring removed bh option EXT4-fs (loop4): inodes count not valid: 131104 vs 32 EXT4-fs (loop4): Ignoring removed bh option overlayfs: fs on './file0' does not support file handles, falling back to index=off,nfs_export=off. EXT4-fs (loop4): inodes count not valid: 196640 vs 32 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 IPVS: ftp: loaded support on port[0] = 21 EXT4-fs (loop4): Ignoring removed bh option EXT4-fs (loop4): inodes count not valid: 262176 vs 32 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 (loop4): Ignoring removed bh option EXT4-fs (loop4): inodes count not valid: 327712 vs 32 EXT4-fs (loop4): Ignoring removed bh option EXT4-fs (loop4): inodes count not valid: 393248 vs 32 batman_adv: The newly added mac address (aa:aa:aa:aa:aa:3d) already exists on: batadv_slave_0 batman_adv: It is strongly recommended to keep mac addresses unique to avoid problems! EXT4-fs (loop4): Ignoring removed bh option EXT4-fs (loop4): inodes count not valid: 458784 vs 32 batman_adv: The newly added mac address (aa:aa:aa:aa:aa:3d) already exists on: batadv_slave_0 batman_adv: It is strongly recommended to keep mac addresses unique to avoid problems! batman_adv: The newly added mac address (aa:aa:aa:aa:aa:3d) already exists on: batadv_slave_0 batman_adv: It is strongly recommended to keep mac addresses unique to avoid problems! batman_adv: The newly added mac address (aa:aa:aa:aa:aa:3d) already exists on: batadv_slave_0 batman_adv: It is strongly recommended to keep mac addresses unique to avoid problems! EXT4-fs (loop4): Ignoring removed bh option EXT4-fs (loop4): inodes count not valid: 524320 vs 32 EXT4-fs (loop4): Ignoring removed bh option EXT4-fs (loop4): inodes count not valid: 589856 vs 32 EXT4-fs (loop4): Ignoring removed bh option EXT4-fs (loop4): inodes count not valid: 655392 vs 32 EXT4-fs (loop4): Ignoring removed bh option EXT4-fs (loop4): inodes count not valid: 1114144 vs 32 EXT4-fs (loop4): Ignoring removed bh option EXT4-fs (loop4): inodes count not valid: 1245216 vs 32 EXT4-fs (loop4): Ignoring removed bh option EXT4-fs (loop4): inodes count not valid: 1572896 vs 32 EXT4-fs (loop4): Ignoring removed bh option EXT4-fs (loop4): inodes count not valid: 2293792 vs 32