FAT-fs (loop4): Directory bread(block 4) failed ====================================================== WARNING: possible circular locking dependency detected 4.14.294-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.2/10319 is trying to acquire lock: (&ovl_i_mutex_dir_key[depth]){++++}, at: [] inode_lock_shared include/linux/fs.h:729 [inline] (&ovl_i_mutex_dir_key[depth]){++++}, at: [] lookup_slow+0x129/0x400 fs/namei.c:1674 but task is already holding lock: (&oi->lock){+.+.}, at: [] ovl_nlink_start+0x22f/0x460 fs/overlayfs/util.c:523 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (&oi->lock){+.+.}: __mutex_lock_common kernel/locking/mutex.c:756 [inline] __mutex_lock+0xc4/0x1310 kernel/locking/mutex.c:893 ovl_copy_up_start+0x40/0xe0 fs/overlayfs/util.c:318 ovl_copy_up_one+0x21f/0x910 fs/overlayfs/copy_up.c:631 ovl_copy_up_flags+0xd5/0x120 fs/overlayfs/copy_up.c:686 ovl_create_or_link+0xa2/0x1200 fs/overlayfs/dir.c:476 ovl_create_object+0x17b/0x1d0 fs/overlayfs/dir.c:550 lookup_open+0x77a/0x1750 fs/namei.c:3241 do_last fs/namei.c:3334 [inline] path_openat+0xe08/0x2970 fs/namei.c:3571 do_filp_open+0x179/0x3c0 fs/namei.c:3605 do_sys_open+0x296/0x410 fs/open.c:1081 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x46/0xbb -> #1 (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+0x64/0x260 fs/super.c:1342 sb_start_write include/linux/fs.h:1551 [inline] mnt_want_write+0x3a/0xb0 fs/namespace.c:386 ovl_create_object+0x75/0x1d0 fs/overlayfs/dir.c:538 lookup_open+0x77a/0x1750 fs/namei.c:3241 do_last fs/namei.c:3334 [inline] path_openat+0xe08/0x2970 fs/namei.c:3571 do_filp_open+0x179/0x3c0 fs/namei.c:3605 do_sys_open+0x296/0x410 fs/open.c:1081 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x46/0xbb -> #0 (&ovl_i_mutex_dir_key[depth]){++++}: lock_acquire+0x170/0x3f0 kernel/locking/lockdep.c:3998 down_read+0x36/0x80 kernel/locking/rwsem.c:24 inode_lock_shared include/linux/fs.h:729 [inline] lookup_slow+0x129/0x400 fs/namei.c:1674 lookup_one_len_unlocked+0x3a0/0x410 fs/namei.c:2595 ovl_lower_positive+0x184/0x350 fs/overlayfs/namei.c:783 ovl_rename+0x47c/0xe50 fs/overlayfs/dir.c:968 vfs_rename+0x560/0x1820 fs/namei.c:4498 SYSC_renameat2 fs/namei.c:4646 [inline] SyS_renameat2+0x95b/0xad0 fs/namei.c:4535 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x46/0xbb other info that might help us debug this: Chain exists of: &ovl_i_mutex_dir_key[depth] --> sb_writers#3 --> &oi->lock Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&oi->lock); lock(sb_writers#3); lock(&oi->lock); lock(&ovl_i_mutex_dir_key[depth]); *** DEADLOCK *** 8 locks held by syz-executor.2/10319: #0: (sb_writers#13){.+.+}, at: [] sb_start_write include/linux/fs.h:1551 [inline] #0: (sb_writers#13){.+.+}, at: [] mnt_want_write+0x3a/0xb0 fs/namespace.c:386 #1: (&type->s_vfs_rename_key#2){+.+.}, at: [] lock_rename+0x54/0x280 fs/namei.c:2889 #2: (&ovl_i_mutex_dir_key[depth]#2/1){+.+.}, at: [] inode_lock_nested include/linux/fs.h:754 [inline] #2: (&ovl_i_mutex_dir_key[depth]#2/1){+.+.}, at: [] lock_rename+0xa0/0x280 fs/namei.c:2893 #3: (&ovl_i_mutex_dir_key[depth]#2/2){+.+.}, at: [] inode_lock_nested include/linux/fs.h:754 [inline] #3: (&ovl_i_mutex_dir_key[depth]#2/2){+.+.}, at: [] lock_rename+0xd4/0x280 fs/namei.c:2894 #4: (&ovl_i_mutex_key[depth]){+.+.}, at: [] inode_lock include/linux/fs.h:719 [inline] #4: (&ovl_i_mutex_key[depth]){+.+.}, at: [] lock_two_nondirectories+0xca/0xf0 fs/inode.c:990 #5: (&ovl_i_mutex_key[depth]/4){+.+.}, at: [] inode_lock_nested include/linux/fs.h:754 [inline] #5: (&ovl_i_mutex_key[depth]/4){+.+.}, at: [] lock_two_nondirectories+0xb2/0xf0 fs/inode.c:992 #6: (sb_writers#3){.+.+}, at: [] sb_start_write include/linux/fs.h:1551 [inline] #6: (sb_writers#3){.+.+}, at: [] mnt_want_write+0x3a/0xb0 fs/namespace.c:386 #7: (&oi->lock){+.+.}, at: [] ovl_nlink_start+0x22f/0x460 fs/overlayfs/util.c:523 stack backtrace: CPU: 1 PID: 10319 Comm: syz-executor.2 Not tainted 4.14.294-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/26/2022 Call Trace: __dump_stack lib/dump_stack.c:17 [inline] dump_stack+0x1b2/0x281 lib/dump_stack.c:58 print_circular_bug.constprop.0.cold+0x2d7/0x41e kernel/locking/lockdep.c:1258 check_prev_add kernel/locking/lockdep.c:1905 [inline] check_prevs_add kernel/locking/lockdep.c:2022 [inline] validate_chain kernel/locking/lockdep.c:2464 [inline] __lock_acquire+0x2e0e/0x3f20 kernel/locking/lockdep.c:3491 lock_acquire+0x170/0x3f0 kernel/locking/lockdep.c:3998 down_read+0x36/0x80 kernel/locking/rwsem.c:24 inode_lock_shared include/linux/fs.h:729 [inline] lookup_slow+0x129/0x400 fs/namei.c:1674 lookup_one_len_unlocked+0x3a0/0x410 fs/namei.c:2595 ovl_lower_positive+0x184/0x350 fs/overlayfs/namei.c:783 ovl_rename+0x47c/0xe50 fs/overlayfs/dir.c:968 vfs_rename+0x560/0x1820 fs/namei.c:4498 SYSC_renameat2 fs/namei.c:4646 [inline] SyS_renameat2+0x95b/0xad0 fs/namei.c:4535 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x46/0xbb RIP: 0033:0x7f2b5a0df5a9 RSP: 002b:00007f2b58a32168 EFLAGS: 00000246 ORIG_RAX: 0000000000000052 RAX: ffffffffffffffda RBX: 00007f2b5a201050 RCX: 00007f2b5a0df5a9 RDX: 0000000000000000 RSI: 0000000020000240 RDI: 00000000200002c0 RBP: 00007f2b5a13a560 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffc136d427f R14: 00007f2b58a32300 R15: 0000000000022000 unregister_netdevice: waiting for ip6gre0 to become free. Usage count = -1 overlayfs: fs on 'file0' does not support file handles, falling back to index=off. overlayfs: fs on './file0' does not support file handles, falling back to index=off. overlayfs: fs on './file0' does not support file handles, falling back to index=off. overlayfs: fs on 'file0' does not support file handles, falling back to index=off. overlayfs: fs on './file0' does not support file handles, falling back to index=off. overlayfs: fs on 'file0' does not support file handles, falling back to index=off. overlayfs: fs on './file0' does not support file handles, falling back to index=off. overlayfs: fs on './file0' does not support file handles, falling back to index=off. overlayfs: fs on 'file0' does not support file handles, falling back to index=off. overlayfs: fs on './file0' does not support file handles, falling back to index=off. overlayfs: fs on './file0' does not support file handles, falling back to index=off. overlayfs: fs on 'file0' does not support file handles, falling back to index=off. overlayfs: fs on 'file0' does not support file handles, falling back to index=off. overlayfs: fs on './file0' does not support file handles, falling back to index=off. overlayfs: fs on './file0' does not support file handles, falling back to index=off. FAT-fs (loop0): bogus number of reserved sectors FAT-fs (loop0): Can't find a valid FAT filesystem EXT4-fs (loop2): filesystem too large to mount safely on this system REISERFS (device loop3): found reiserfs format "3.6" with non-standard journal REISERFS warning (device loop3): reiserfs_fill_super: Filesystem cannot be mounted because it is bigger than the device REISERFS warning (device loop3): reiserfs_fill_super: You may need to run fsck or increase size of your LVM partition REISERFS warning (device loop3): reiserfs_fill_super: Or may be you forgot to reboot after fdisk when it told you to EXT4-fs (loop2): filesystem too large to mount safely on this system EXT4-fs (loop2): filesystem too large to mount safely on this system tmpfs: Bad value 'bind=static' for mount option 'mpol' EXT4-fs (loop2): filesystem too large to mount safely on this system ISO 9660 Extensions: Microsoft Joliet Level 0 print_req_error: I/O error, dev loop0, sector 0 BTRFS info (device loop3): trying to use backup root at mount time BTRFS info (device loop3): enabling free space tree BTRFS info (device loop3): using free space tree BTRFS info (device loop3): has skinny extents BTRFS warning (device loop3): loop3 checksum verify failed on 30420992 wanted 538FDB82 found ABC4B005 level 0 BTRFS info (device loop3): read error corrected: ino 0 off 30420992 (dev /dev/loop3 sector 75800) BTRFS info (device loop3): creating free space tree BTRFS info (device loop3): setting 1 ro feature flag BTRFS info (device loop3): setting 2 ro feature flag attempt to access beyond end of device loop3: rw=6145, want=141392, limit=141367 BTRFS error (device loop3): bdev /dev/loop3 errs: wr 1, rd 0, flush 0, corrupt 0, gen 0 BTRFS: error (device loop3) in btrfs_commit_transaction:2280: errno=-5 IO failure (Error while writing out transaction) BTRFS warning (device loop3): Skipping commit of aborted transaction. BTRFS: error (device loop3) in cleanup_transaction:1883: errno=-5 IO failure BTRFS info (device loop3): delayed_refs has NO entry FAT-fs (loop2): bogus number of reserved sectors FAT-fs (loop2): Can't find a valid FAT filesystem BTRFS warning (device loop3): failed to create free space tree: -5 ISO 9660 Extensions: Microsoft Joliet Level 0 BTRFS error (device loop3): commit super ret -30 BTRFS error (device loop3): open_ctree failed ISO 9660 Extensions: Microsoft Joliet Level 0 print_req_error: I/O error, dev loop0, sector 0 ISO 9660 Extensions: Microsoft Joliet Level 0 FAT-fs (loop2): Directory bread(block 3) failed FAT-fs (loop2): Directory bread(block 4) failed FAT-fs (loop2): Directory bread(block 5) failed FAT-fs (loop2): Directory bread(block 6) failed FAT-fs (loop2): Directory bread(block 3) failed FAT-fs (loop2): Directory bread(block 4) failed FAT-fs (loop2): Directory bread(block 5) failed FAT-fs (loop2): Directory bread(block 6) failed FAT-fs (loop2): Directory bread(block 3) failed FAT-fs (loop2): Directory bread(block 4) failed netlink: 20 bytes leftover after parsing attributes in process `syz-executor.2'. netlink: 20 bytes leftover after parsing attributes in process `syz-executor.2'. netlink: 20 bytes leftover after parsing attributes in process `syz-executor.5'. netlink: 20 bytes leftover after parsing attributes in process `syz-executor.2'. netlink: 20 bytes leftover after parsing attributes in process `syz-executor.2'. netlink: 20 bytes leftover after parsing attributes in process `syz-executor.5'. netlink: 20 bytes leftover after parsing attributes in process `syz-executor.5'. kauditd_printk_skb: 6 callbacks suppressed audit: type=1800 audit(1664348215.331:42): pid=10742 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.4" name="file0" dev="sda1" ino=14061 res=0 audit: type=1804 audit(1664348216.321:43): pid=10778 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.5" name="/root/syzkaller-testdir1077213912/syzkaller.GWG2ZK/33/bus" dev="sda1" ino=14061 res=1 audit: type=1800 audit(1664348216.351:44): pid=10778 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.5" name="bus" dev="sda1" ino=14061 res=0 overlayfs: failed to resolve './file0': -2 audit: type=1804 audit(1664348216.681:45): pid=10806 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.5" name="/root/syzkaller-testdir1077213912/syzkaller.GWG2ZK/34/bus" dev="sda1" ino=14067 res=1 fat__get_entry: 2 callbacks suppressed FAT-fs (loop4): Directory bread(block 3) failed FAT-fs (loop4): Directory bread(block 4) failed FAT-fs (loop4): Directory bread(block 5) failed FAT-fs (loop4): Directory bread(block 6) failed audit: type=1800 audit(1664348218.551:46): pid=10806 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.5" name="bus" dev="sda1" ino=14067 res=0 audit: type=1800 audit(1664348218.811:47): pid=10841 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.4" name="file0" dev="sda1" ino=14053 res=0 audit: type=1804 audit(1664348218.951:48): pid=10858 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.5" name="/root/syzkaller-testdir1077213912/syzkaller.GWG2ZK/35/bus" dev="sda1" ino=14068 res=1 audit: type=1800 audit(1664348218.951:49): pid=10858 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.5" name="bus" dev="sda1" ino=14068 res=0 audit: type=1804 audit(1664348219.871:50): pid=10920 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.5" name="/root/syzkaller-testdir1077213912/syzkaller.GWG2ZK/36/bus" dev="sda1" ino=14053 res=1