UDF-fs: error (device loop3): udf_read_tagged: tag version 0x0000 != 0x0002 || 0x0003, block 0 overlayfs: fs on './file0' does not support file handles, falling back to index=off. UDF-fs: error (device loop3): udf_read_tagged: tag version 0x0000 != 0x0002 || 0x0003, block 0 ====================================================== WARNING: possible circular locking dependency detected 4.14.294-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.5/10031 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: (sb_writers#3){.+.+}, at: [] sb_start_write include/linux/fs.h:1551 [inline] (sb_writers#3){.+.+}, 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#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: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(sb_writers#3); lock(&ovl_i_mutex_dir_key[depth]); lock(sb_writers#3); lock(&ovl_i_mutex_dir_key[depth]); *** DEADLOCK *** 6 locks held by syz-executor.5/10031: #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#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]/4){+.+.}, at: [] inode_lock_nested include/linux/fs.h:754 [inline] #4: (&ovl_i_mutex_key[depth]/4){+.+.}, at: [] lock_two_nondirectories+0xb2/0xf0 fs/inode.c:992 #5: (sb_writers#3){.+.+}, at: [] sb_start_write include/linux/fs.h:1551 [inline] #5: (sb_writers#3){.+.+}, at: [] mnt_want_write+0x3a/0xb0 fs/namespace.c:386 stack backtrace: CPU: 0 PID: 10031 Comm: syz-executor.5 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:0x7fcf82c91669 RSP: 002b:00007fcf81605168 EFLAGS: 00000246 ORIG_RAX: 0000000000000052 RAX: ffffffffffffffda RBX: 00007fcf82db2f80 RCX: 00007fcf82c91669 RDX: 0000000000000000 RSI: 00000000200004c0 RDI: 00000000200002c0 RBP: 00007fcf82cec560 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007fffb43effef R14: 00007fcf81605300 R15: 0000000000022000 UDF-fs: error (device loop3): udf_read_tagged: tag version 0x0000 != 0x0002 || 0x0003, block 0 UDF-fs: warning (device loop3): udf_load_vrs: No anchor found UDF-fs: Scanning with blocksize 1024 failed UDF-fs: error (device loop3): udf_read_tagged: tag version 0x0000 != 0x0002 || 0x0003, block 0 UDF-fs: error (device loop3): udf_read_tagged: tag version 0x0000 != 0x0002 || 0x0003, block 0 UDF-fs: error (device loop3): udf_read_tagged: tag version 0x0000 != 0x0002 || 0x0003, block 0 UDF-fs: warning (device loop3): udf_load_vrs: No anchor found UDF-fs: Scanning with blocksize 2048 failed UDF-fs: error (device loop3): udf_read_tagged: tag version 0x0000 != 0x0002 || 0x0003, block 0 UDF-fs: error (device loop3): udf_read_tagged: read failed, block=512, location=512 UDF-fs: error (device loop3): udf_read_tagged: tag version 0x0000 != 0x0002 || 0x0003, block 0 UDF-fs: error (device loop3): udf_read_tagged: tag version 0x0000 != 0x0002 || 0x0003, block 0 UDF-fs: warning (device loop3): udf_load_vrs: No anchor found UDF-fs: Scanning with blocksize 4096 failed UDF-fs: warning (device loop3): udf_fill_super: No partition found (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. UDF-fs: error (device loop4): udf_process_sequence: Block 96 of volume descriptor sequence is corrupted or we could not read it UDF-fs: error (device loop4): udf_process_sequence: Block 1987 of volume descriptor sequence is corrupted or we could not read it UDF-fs: Scanning with blocksize 512 failed UDF-fs: error (device loop4): udf_read_tagged: tag version 0x0000 != 0x0002 || 0x0003, block 0 UDF-fs: error (device loop4): udf_read_tagged: tag version 0x0000 != 0x0002 || 0x0003, block 0 UDF-fs: error (device loop4): udf_read_tagged: tag version 0x0000 != 0x0002 || 0x0003, block 0 UDF-fs: warning (device loop4): udf_load_vrs: No anchor found UDF-fs: Scanning with blocksize 1024 failed UDF-fs: error (device loop4): udf_read_tagged: tag version 0x0000 != 0x0002 || 0x0003, block 0 UDF-fs: error (device loop4): udf_read_tagged: tag version 0x0000 != 0x0002 || 0x0003, block 0 UDF-fs: error (device loop4): udf_read_tagged: tag version 0x0000 != 0x0002 || 0x0003, block 0 UDF-fs: warning (device loop4): udf_load_vrs: No anchor found UDF-fs: Scanning with blocksize 2048 failed UDF-fs: error (device loop4): udf_read_tagged: tag version 0x0000 != 0x0002 || 0x0003, block 0 UDF-fs: error (device loop4): udf_read_tagged: read failed, block=512, location=512 UDF-fs: error (device loop4): udf_read_tagged: tag version 0x0000 != 0x0002 || 0x0003, block 0 UDF-fs: error (device loop4): udf_read_tagged: tag version 0x0000 != 0x0002 || 0x0003, block 0 UDF-fs: warning (device loop4): udf_load_vrs: No anchor found UDF-fs: Scanning with blocksize 4096 failed UDF-fs: warning (device loop4): udf_fill_super: No partition found (1) EXT4-fs warning (device sda1): verify_group_input:146: Cannot add at group 1 (only 16 groups) overlayfs: failed to resolve './file1': -2 kvm: vcpu 0: requested 128 ns lapic timer period limited to 500000 ns overlayfs: failed to resolve './file1': -2 overlayfs: failed to resolve './file1': -2 kvm: vcpu 0: requested 128 ns lapic timer period limited to 500000 ns overlayfs: failed to resolve './file0': -2 overlayfs: failed to resolve './file0': -2 kvm: vcpu 0: requested 128 ns lapic timer period limited to 500000 ns overlayfs: failed to resolve './file0': -2 overlayfs: failed to resolve './file0': -2 kvm: vcpu 0: requested 128 ns lapic timer period limited to 500000 ns overlayfs: failed to resolve './file0': -2 kvm: vcpu 0: requested 128 ns lapic timer period limited to 500000 ns overlayfs: failed to resolve './file0': -2 overlayfs: failed to resolve './file1': -2 kvm: vcpu 0: requested 128 ns lapic timer period limited to 500000 ns overlayfs: failed to resolve './file1': -2 overlayfs: failed to resolve './file1': -2 kvm: vcpu 0: requested 128 ns lapic timer period limited to 500000 ns kvm: vcpu 0: requested 128 ns lapic timer period limited to 500000 ns overlayfs: missing 'lowerdir' kvm: vcpu 0: requested 128 ns lapic timer period limited to 500000 ns overlayfs: missing 'lowerdir' kvm: vcpu 0: requested 128 ns lapic timer period limited to 500000 ns overlayfs: missing 'lowerdir' overlayfs: missing 'lowerdir' overlayfs: missing 'lowerdir' IPVS: ftp: loaded support on port[0] = 21 overlayfs: missing 'lowerdir' overlayfs: missing 'lowerdir' overlayfs: missing 'lowerdir' IPVS: ftp: loaded support on port[0] = 21 overlayfs: missing 'lowerdir' overlayfs: missing 'lowerdir' overlayfs: missing 'lowerdir' overlayfs: missing 'lowerdir' overlayfs: unrecognized mount option "lower" or missing value overlayfs: unrecognized mount option "lower" or missing value