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. ====================================================== WARNING: possible circular locking dependency detected 4.14.307-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.5/10367 is trying to acquire lock: (&ovl_i_mutex_dir_key[depth]){++++}, at: [] iterate_dir+0x387/0x5e0 fs/readdir.c:43 but task is already holding lock: (sb_writers#6){.+.+}, at: [] sb_start_write include/linux/fs.h:1551 [inline] (sb_writers#6){.+.+}, at: [] mnt_want_write+0x3a/0xb0 fs/namespace.c:386 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (sb_writers#6){.+.+}: 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_xattr_set+0x4d/0x290 fs/overlayfs/inode.c:214 ovl_posix_acl_xattr_set+0x2b7/0x830 fs/overlayfs/super.c:762 __vfs_setxattr+0xdc/0x130 fs/xattr.c:150 __vfs_setxattr_noperm+0xfd/0x3d0 fs/xattr.c:181 __vfs_setxattr_locked+0x14d/0x250 fs/xattr.c:239 vfs_setxattr+0xcf/0x230 fs/xattr.c:256 setxattr+0x1a9/0x300 fs/xattr.c:523 path_setxattr+0x118/0x130 fs/xattr.c:542 SYSC_lsetxattr fs/xattr.c:564 [inline] SyS_lsetxattr+0x33/0x40 fs/xattr.c:560 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x5e/0xd3 -> #0 (&ovl_i_mutex_dir_key[depth]){++++}: lock_acquire+0x170/0x3f0 kernel/locking/lockdep.c:3998 down_write_killable+0x37/0xb0 kernel/locking/rwsem.c:68 iterate_dir+0x387/0x5e0 fs/readdir.c:43 ovl_dir_read fs/overlayfs/readdir.c:306 [inline] ovl_dir_read_merged+0x2c5/0x430 fs/overlayfs/readdir.c:365 ovl_check_empty_dir+0x6e/0x200 fs/overlayfs/readdir.c:870 ovl_check_empty_and_clear+0x72/0xe0 fs/overlayfs/dir.c:306 ovl_rename+0x57d/0xe50 fs/overlayfs/dir.c:959 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+0x5e/0xd3 other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(sb_writers#6); lock(&ovl_i_mutex_dir_key[depth]); lock(sb_writers#6); lock(&ovl_i_mutex_dir_key[depth]); *** DEADLOCK *** 6 locks held by syz-executor.5/10367: #0: (sb_writers#15){.+.+}, at: [] sb_start_write include/linux/fs.h:1551 [inline] #0: (sb_writers#15){.+.+}, at: [] mnt_want_write+0x3a/0xb0 fs/namespace.c:386 #1: (&type->s_vfs_rename_key#3){+.+.}, 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+0x132/0x280 fs/namei.c:2900 #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+0x166/0x280 fs/namei.c:2901 #4: (&ovl_i_mutex_dir_key[depth]#2){++++}, at: [] inode_lock include/linux/fs.h:719 [inline] #4: (&ovl_i_mutex_dir_key[depth]#2){++++}, at: [] vfs_rename+0xbd8/0x1820 fs/namei.c:4472 #5: (sb_writers#6){.+.+}, at: [] sb_start_write include/linux/fs.h:1551 [inline] #5: (sb_writers#6){.+.+}, at: [] mnt_want_write+0x3a/0xb0 fs/namespace.c:386 stack backtrace: CPU: 0 PID: 10367 Comm: syz-executor.5 Not tainted 4.14.307-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/16/2023 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_write_killable+0x37/0xb0 kernel/locking/rwsem.c:68 iterate_dir+0x387/0x5e0 fs/readdir.c:43 ovl_dir_read fs/overlayfs/readdir.c:306 [inline] ovl_dir_read_merged+0x2c5/0x430 fs/overlayfs/readdir.c:365 ovl_check_empty_dir+0x6e/0x200 fs/overlayfs/readdir.c:870 ovl_check_empty_and_clear+0x72/0xe0 fs/overlayfs/dir.c:306 ovl_rename+0x57d/0xe50 fs/overlayfs/dir.c:959 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+0x5e/0xd3 RIP: 0033:0x7fbfc7d7b0f9 RSP: 002b:00007fbfc62ed168 EFLAGS: 00000246 ORIG_RAX: 0000000000000052 RAX: ffffffffffffffda RBX: 00007fbfc7e9af80 RCX: 00007fbfc7d7b0f9 RDX: 0000000000000000 RSI: 0000000020000440 RDI: 0000000020000100 RBP: 00007fbfc7dd6ae9 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffffea6814f R14: 00007fbfc62ed300 R15: 0000000000022000 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. syz-executor.5 (10367) used greatest stack depth: 24768 bytes left 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. EXT4-fs (loop2): Ignoring removed mblk_io_submit option EXT4-fs (loop2): Unsupported blocksize for fs encryption EXT4-fs (loop2): Ignoring removed mblk_io_submit option EXT4-fs (loop2): Unsupported blocksize for fs encryption EXT4-fs (loop2): Ignoring removed mblk_io_submit option EXT4-fs (loop2): Unsupported blocksize for fs encryption print_req_error: I/O error, dev loop2, sector 0 Buffer I/O error on dev loop2, logical block 0, async page read print_req_error: I/O error, dev loop2, sector 6 Buffer I/O error on dev loop2, logical block 3, async page read EXT4-fs (loop2): Ignoring removed mblk_io_submit option EXT4-fs (loop2): Unsupported blocksize for fs encryption print_req_error: I/O error, dev loop2, sector 0 Buffer I/O error on dev loop2, logical block 0, async page read print_req_error: I/O error, dev loop2, sector 6 Buffer I/O error on dev loop2, logical block 3, async page read EXT4-fs (loop1): mounted filesystem without journal. Opts: ,errors=continue XFS (loop0): Mounting V4 Filesystem XFS (loop0): Ending clean mount syz-executor.0 (10711) used greatest stack depth: 24080 bytes left XFS (loop0): Unmounting Filesystem EXT4-fs (loop1): mounted filesystem without journal. Opts: ,errors=continue XFS (loop0): Mounting V4 Filesystem EXT4-fs (loop5): mounted filesystem without journal. Opts: ,errors=continue XFS (loop2): Mounting V4 Filesystem XFS (loop2): Ending clean mount XFS (loop0): Ending clean mount XFS (loop4): Mounting V4 Filesystem EXT4-fs (loop1): mounted filesystem without journal. Opts: ,errors=continue XFS (loop4): Ending clean mount XFS (loop0): Unmounting Filesystem syz-executor.2 (10784) used greatest stack depth: 23232 bytes left XFS (loop2): Unmounting Filesystem XFS (loop4): Unmounting Filesystem EXT4-fs (loop5): mounted filesystem without journal. Opts: ,errors=continue EXT4-fs (loop1): mounted filesystem without journal. Opts: ,errors=continue EXT4-fs (loop5): mounted filesystem without journal. Opts: ,errors=continue