NILFS (loop2): segctord starting. Construction interval = 5 seconds, CP frequency < 30 seconds NILFS error (device loop2): nilfs_ifile_get_inode_block: bad inode number: 1 ====================================================== WARNING: possible circular locking dependency detected 4.19.211-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.2/31415 is trying to acquire lock: 00000000d4ebd1a4 (&nilfs->ns_sem){++++}, at: nilfs_set_error fs/nilfs2/super.c:86 [inline] 00000000d4ebd1a4 (&nilfs->ns_sem){++++}, at: __nilfs_error+0x195/0x401 fs/nilfs2/super.c:131 but task is already holding lock: 000000005f74579d (&dat_lock_key){.+.+}, at: __nilfs_read_inode fs/nilfs2/inode.c:482 [inline] 000000005f74579d (&dat_lock_key){.+.+}, at: nilfs_iget+0x1cf/0x860 fs/nilfs2/inode.c:592 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&dat_lock_key){.+.+}: nilfs_count_free_blocks+0x68/0x180 fs/nilfs2/the_nilfs.c:698 nilfs_set_log_cursor fs/nilfs2/super.c:237 [inline] nilfs_cleanup_super+0x133/0x490 fs/nilfs2/super.c:319 load_nilfs+0x79f/0x11f0 fs/nilfs2/the_nilfs.c:317 nilfs_fill_super fs/nilfs2/super.c:1063 [inline] nilfs_mount+0x9b5/0xe70 fs/nilfs2/super.c:1321 mount_fs+0xa3/0x310 fs/super.c:1261 vfs_kern_mount.part.0+0x68/0x470 fs/namespace.c:961 vfs_kern_mount fs/namespace.c:951 [inline] do_new_mount fs/namespace.c:2492 [inline] do_mount+0x115c/0x2f50 fs/namespace.c:2822 ksys_mount+0xcf/0x130 fs/namespace.c:3038 __do_sys_mount fs/namespace.c:3052 [inline] __se_sys_mount fs/namespace.c:3049 [inline] __x64_sys_mount+0xba/0x150 fs/namespace.c:3049 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe -> #0 (&nilfs->ns_sem){++++}: down_write+0x34/0x90 kernel/locking/rwsem.c:70 nilfs_set_error fs/nilfs2/super.c:86 [inline] __nilfs_error+0x195/0x401 fs/nilfs2/super.c:131 nilfs_ifile_get_inode_block+0x12a/0x170 fs/nilfs2/ifile.c:139 __nilfs_read_inode fs/nilfs2/inode.c:483 [inline] nilfs_iget+0x204/0x860 fs/nilfs2/inode.c:592 nilfs_lookup fs/nilfs2/namei.c:63 [inline] nilfs_lookup+0xfd/0x130 fs/nilfs2/namei.c:54 lookup_open+0x698/0x1a20 fs/namei.c:3214 do_last fs/namei.c:3327 [inline] path_openat+0x1804/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 other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&dat_lock_key); lock(&nilfs->ns_sem); lock(&dat_lock_key); lock(&nilfs->ns_sem); *** DEADLOCK *** 2 locks held by syz-executor.2/31415: #0: 00000000fc4990a2 (&type->i_mutex_dir_key#15){.+.+}, at: inode_lock_shared include/linux/fs.h:758 [inline] #0: 00000000fc4990a2 (&type->i_mutex_dir_key#15){.+.+}, at: do_last fs/namei.c:3326 [inline] #0: 00000000fc4990a2 (&type->i_mutex_dir_key#15){.+.+}, at: path_openat+0x17ec/0x2df0 fs/namei.c:3537 #1: 000000005f74579d (&dat_lock_key){.+.+}, at: __nilfs_read_inode fs/nilfs2/inode.c:482 [inline] #1: 000000005f74579d (&dat_lock_key){.+.+}, at: nilfs_iget+0x1cf/0x860 fs/nilfs2/inode.c:592 stack backtrace: CPU: 1 PID: 31415 Comm: syz-executor.2 Not tainted 4.19.211-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022 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 down_write+0x34/0x90 kernel/locking/rwsem.c:70 nilfs_set_error fs/nilfs2/super.c:86 [inline] __nilfs_error+0x195/0x401 fs/nilfs2/super.c:131 nilfs_ifile_get_inode_block+0x12a/0x170 fs/nilfs2/ifile.c:139 __nilfs_read_inode fs/nilfs2/inode.c:483 [inline] nilfs_iget+0x204/0x860 fs/nilfs2/inode.c:592 nilfs_lookup fs/nilfs2/namei.c:63 [inline] nilfs_lookup+0xfd/0x130 fs/nilfs2/namei.c:54 lookup_open+0x698/0x1a20 fs/namei.c:3214 do_last fs/namei.c:3327 [inline] path_openat+0x1804/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 RIP: 0033:0x7f2d6d4740a9 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 90 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:00007f2d6b9e6168 EFLAGS: 00000246 ORIG_RAX: 0000000000000101 RAX: ffffffffffffffda RBX: 00007f2d6d593f80 RCX: 00007f2d6d4740a9 RDX: 0000000000000000 RSI: 00000000200003c0 RDI: 0000000000000006 RBP: 00007f2d6d4cfae9 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffeeeb8e4ff R14: 00007f2d6b9e6300 R15: 0000000000022000 Remounting filesystem read-only NILFS (loop2): segctord starting. Construction interval = 5 seconds, CP frequency < 30 seconds IPVS: ftp: loaded support on port[0] = 21 netlink: 40 bytes leftover after parsing attributes in process `syz-executor.4'. netlink: 40 bytes leftover after parsing attributes in process `syz-executor.4'. netlink: 40 bytes leftover after parsing attributes in process `syz-executor.4'. x_tables: duplicate underflow at hook 2 x_tables: duplicate underflow at hook 2 x_tables: duplicate underflow at hook 2 netlink: 24 bytes leftover after parsing attributes in process `syz-executor.1'.