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.296-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.2/12000 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_link+0x9b/0x190 fs/overlayfs/dir.c:598 vfs_link+0x6d5/0xb40 fs/namei.c:4266 SYSC_linkat fs/namei.c:4334 [inline] SyS_linkat+0x3e5/0x6a0 fs/namei.c:4290 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/12000: #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+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]#2){+.+.}, at: [] inode_lock include/linux/fs.h:719 [inline] #4: (&ovl_i_mutex_key[depth]#2){+.+.}, at: [] lock_two_nondirectories+0xca/0xf0 fs/inode.c:989 #5: (&ovl_i_mutex_key[depth]#2/4){+.+.}, at: [] inode_lock_nested include/linux/fs.h:754 [inline] #5: (&ovl_i_mutex_key[depth]#2/4){+.+.}, at: [] lock_two_nondirectories+0xb2/0xf0 fs/inode.c:991 #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: 0 PID: 12000 Comm: syz-executor.2 Not tainted 4.14.296-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/11/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:0x7fda6032a5a9 RSP: 002b:00007fda5e89d168 EFLAGS: 00000246 ORIG_RAX: 0000000000000052 RAX: ffffffffffffffda RBX: 00007fda6044af80 RCX: 00007fda6032a5a9 RDX: 0000000000000000 RSI: 0000000020000440 RDI: 0000000020000380 RBP: 00007fda603857b0 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffe8c0a998f R14: 00007fda5e89d300 R15: 0000000000022000 kauditd_printk_skb: 2 callbacks suppressed audit: type=1800 audit(1666893036.530:26): pid=12032 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.2" name="bus" dev="loop2" ino=8 res=0 ====================================================== WARNING: the mand mount option is being deprecated and will be removed in v5.15! ====================================================== print_req_error: I/O error, dev loop0, sector 0 netlink: 24 bytes leftover after parsing attributes in process `syz-executor.4'. Zero length message leads to an empty skb print_req_error: I/O error, dev loop1, sector 0 print_req_error: I/O error, dev loop1, sector 24 BTRFS: device fsid da33867d-e382-4163-b5e0-ea15c91cfb38 devid 1 transid 7 /dev/loop4 BTRFS info (device loop4): enabling free space tree print_req_error: I/O error, dev loop2, sector 0 BTRFS info (device loop4): using free space tree BTRFS info (device loop4): has skinny extents print_req_error: I/O error, dev loop1, sector 0 print_req_error: I/O error, dev loop2, sector 0 BTRFS warning (device loop4): loop4 checksum verify failed on 30420992 wanted 538FDB82 found ABC4B005 level 0 BTRFS info (device loop4): read error corrected: ino 0 off 30420992 (dev /dev/loop4 sector 75800) BTRFS info (device loop4): creating free space tree BTRFS info (device loop4): setting 1 ro feature flag BTRFS info (device loop4): setting 2 ro feature flag BTRFS info (device loop4): checking UUID tree overlayfs: fs on 'file0' does not support file handles, falling back to index=off. sctp: [Deprecated]: syz-executor.0 (pid 12248) Use of struct sctp_assoc_value in delayed_ack socket option. Use struct sctp_sack_info instead overlayfs: fs on './file0' does not support file handles, falling back to index=off. sctp: [Deprecated]: syz-executor.0 (pid 12270) Use of struct sctp_assoc_value in delayed_ack socket option. Use struct sctp_sack_info instead overlayfs: fs on 'file0' does not support file handles, falling back to index=off. sctp: [Deprecated]: syz-executor.2 (pid 12305) Use of struct sctp_assoc_value in delayed_ack socket option. Use struct sctp_sack_info instead 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. sctp: [Deprecated]: syz-executor.0 (pid 12310) Use of struct sctp_assoc_value in delayed_ack socket option. Use struct sctp_sack_info instead 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. sctp: [Deprecated]: syz-executor.2 (pid 12317) Use of struct sctp_assoc_value in delayed_ack socket option. Use struct sctp_sack_info instead 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. sctp: [Deprecated]: syz-executor.0 (pid 12338) Use of struct sctp_assoc_value in delayed_ack socket option. Use struct sctp_sack_info instead overlayfs: fs on './file0' does not support file handles, falling back to index=off. sctp: [Deprecated]: syz-executor.2 (pid 12350) Use of struct sctp_assoc_value in delayed_ack socket option. Use struct sctp_sack_info instead 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. 9pnet: Could not find request transport: xen 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. 9pnet: Could not find request transport: xen overlayfs: fs on './file0' does not support file handles, falling back to index=off. 9pnet: Could not find request transport: xen 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. 9pnet: Could not find request transport: xen overlayfs: fs on './file0' does not support file handles, falling back to index=off. 9pnet: Could not find request transport: xen 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. Bearer <> rejected, not supported in standalone mode 9pnet: Could not find request transport: xen overlayfs: fs on './file0' does not support file handles, falling back to index=off. 9pnet: Could not find request transport: xen unregister_netdevice: waiting for ip6gre0 to become free. Usage count = -1 BTRFS: device fsid 8ff932b8-f4e4-4b03-aed6-d7e5736fd60a devid 1 transid 8 /dev/loop3 BTRFS error (device loop3): unsupported checksum algorithm 1 BTRFS error (device loop3): superblock checksum mismatch BTRFS error (device loop3): open_ctree failed 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. irq bypass consumer (token ffff8880a41e9a00) registration fails: -16