NILFS (loop4): segctord starting. Construction interval = 5 seconds, CP frequency < 30 seconds ====================================================== WARNING: possible circular locking dependency detected 4.14.296-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.4/7998 is trying to acquire lock: (&dat_lock_key){.+.+}, at: [] nilfs_count_free_blocks+0x68/0x180 fs/nilfs2/the_nilfs.c:707 but task is already holding lock: (&nilfs->ns_sem){++++}, at: [] nilfs_put_super+0x139/0x190 fs/nilfs2/super.c:483 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&nilfs->ns_sem){++++}: down_write+0x34/0x90 kernel/locking/rwsem.c:54 nilfs_set_error fs/nilfs2/super.c:95 [inline] __nilfs_error+0x176/0x399 fs/nilfs2/super.c:140 nilfs_bmap_convert_error fs/nilfs2/bmap.c:44 [inline] nilfs_bmap_lookup_contig+0x130/0x170 fs/nilfs2/bmap.c:104 nilfs_get_block+0x1bd/0x7a0 fs/nilfs2/inode.c:93 block_truncate_page+0x2a8/0x8f0 fs/buffer.c:2944 nilfs_truncate+0x204/0x450 fs/nilfs2/inode.c:896 nilfs_setattr+0x1d8/0x220 fs/nilfs2/inode.c:993 notify_change+0x56b/0xd10 fs/attr.c:315 do_truncate+0xff/0x1a0 fs/open.c:63 vfs_truncate+0x456/0x680 fs/open.c:120 do_sys_truncate.part.0+0xdc/0xf0 fs/open.c:143 do_sys_truncate fs/open.c:137 [inline] SYSC_truncate fs/open.c:155 [inline] SyS_truncate+0x23/0x40 fs/open.c:153 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x46/0xbb -> #0 (&dat_lock_key){.+.+}: lock_acquire+0x170/0x3f0 kernel/locking/lockdep.c:3998 down_read+0x36/0x80 kernel/locking/rwsem.c:24 nilfs_count_free_blocks+0x68/0x180 fs/nilfs2/the_nilfs.c:707 nilfs_set_log_cursor fs/nilfs2/super.c:248 [inline] nilfs_cleanup_super+0x123/0x450 fs/nilfs2/super.c:330 nilfs_put_super+0x141/0x190 fs/nilfs2/super.c:484 generic_shutdown_super+0x144/0x370 fs/super.c:446 kill_block_super+0x95/0xe0 fs/super.c:1161 deactivate_locked_super+0x6c/0xd0 fs/super.c:319 deactivate_super+0x7f/0xa0 fs/super.c:350 cleanup_mnt+0x186/0x2c0 fs/namespace.c:1183 task_work_run+0x11f/0x190 kernel/task_work.c:113 tracehook_notify_resume include/linux/tracehook.h:191 [inline] exit_to_usermode_loop+0x1ad/0x200 arch/x86/entry/common.c:164 prepare_exit_to_usermode arch/x86/entry/common.c:199 [inline] syscall_return_slowpath arch/x86/entry/common.c:270 [inline] do_syscall_64+0x4a3/0x640 arch/x86/entry/common.c:297 entry_SYSCALL_64_after_hwframe+0x46/0xbb other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&nilfs->ns_sem); lock(&dat_lock_key); lock(&nilfs->ns_sem); lock(&dat_lock_key); *** DEADLOCK *** 2 locks held by syz-executor.4/7998: #0: (&type->s_umount_key#50){+.+.}, at: [] deactivate_super+0x77/0xa0 fs/super.c:349 #1: (&nilfs->ns_sem){++++}, at: [] nilfs_put_super+0x139/0x190 fs/nilfs2/super.c:483 stack backtrace: CPU: 0 PID: 7998 Comm: syz-executor.4 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 nilfs_count_free_blocks+0x68/0x180 fs/nilfs2/the_nilfs.c:707 nilfs_set_log_cursor fs/nilfs2/super.c:248 [inline] nilfs_cleanup_super+0x123/0x450 fs/nilfs2/super.c:330 nilfs_put_super+0x141/0x190 fs/nilfs2/super.c:484 generic_shutdown_super+0x144/0x370 fs/super.c:446 kill_block_super+0x95/0xe0 fs/super.c:1161 deactivate_locked_super+0x6c/0xd0 fs/super.c:319 deactivate_super+0x7f/0xa0 fs/super.c:350 cleanup_mnt+0x186/0x2c0 fs/namespace.c:1183 task_work_run+0x11f/0x190 kernel/task_work.c:113 tracehook_notify_resume include/linux/tracehook.h:191 [inline] exit_to_usermode_loop+0x1ad/0x200 arch/x86/entry/common.c:164 prepare_exit_to_usermode arch/x86/entry/common.c:199 [inline] syscall_return_slowpath arch/x86/entry/common.c:270 [inline] do_syscall_64+0x4a3/0x640 arch/x86/entry/common.c:297 entry_SYSCALL_64_after_hwframe+0x46/0xbb RIP: 0033:0x7f25b9ed4a17 RSP: 002b:00007ffd2b64d888 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6 RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007f25b9ed4a17 RDX: 00007ffd2b64d95a RSI: 000000000000000a RDI: 00007ffd2b64d950 RBP: 00007ffd2b64d950 R08: 00000000ffffffff R09: 00007ffd2b64d720 R10: 00005555568fd903 R11: 0000000000000246 R12: 00007f25b9f2d826 R13: 00007ffd2b64ea10 R14: 00005555568fd810 R15: 00007ffd2b64ea50 F2FS-fs (loop5): Invalid blocksize (65536), supports only 4KB F2FS-fs (loop5): Can't find valid F2FS filesystem in 1th superblock IPVS: length: 247 != 24 F2FS-fs (loop5): Found nat_bits in checkpoint F2FS-fs (loop5): Mounted with checkpoint version = 3e17dab1 EXT4-fs (loop3): Ignoring removed nobh option EXT4-fs (loop3): Invalid want_extra_isize 3 print_req_error: I/O error, dev loop3, sector 0 Buffer I/O error on dev loop3, logical block 0, async page read print_req_error: I/O error, dev loop3, sector 4 Buffer I/O error on dev loop3, logical block 2, async page read print_req_error: I/O error, dev loop3, sector 6 Buffer I/O error on dev loop3, logical block 3, async page read ISO 9660 Extensions: Microsoft Joliet Level 3 vhci_hcd: Failed attach request for unsupported USB speed: UNKNOWN syz-executor.5 (10358) used greatest stack depth: 25168 bytes left vhci_hcd: Failed attach request for unsupported USB speed: UNKNOWN vhci_hcd: Failed attach request for unsupported USB speed: UNKNOWN vhci_hcd: Failed attach request for unsupported USB speed: UNKNOWN vhci_hcd: Failed attach request for unsupported USB speed: UNKNOWN vhci_hcd vhci_hcd.0: pdev(1) rhport(0) sockfd(4) vhci_hcd vhci_hcd.0: devid(0) speed(4) speed_str(wireless) vhci_hcd vhci_hcd.0: Device attached vhci_hcd: connection closed vhci_hcd: stop threads vhci_hcd: release socket vhci_hcd: disconnect device vhci_hcd: Failed attach request for unsupported USB speed: UNKNOWN vhci_hcd vhci_hcd.0: pdev(1) rhport(0) sockfd(4) vhci_hcd vhci_hcd.0: devid(0) speed(4) speed_str(wireless) vhci_hcd vhci_hcd.0: Device attached vhci_hcd: connection closed vhci_hcd: stop threads vhci_hcd: release socket vhci_hcd: disconnect device vhci_hcd: Failed attach request for unsupported USB speed: UNKNOWN vhci_hcd vhci_hcd.0: pdev(1) rhport(0) sockfd(4) vhci_hcd vhci_hcd.0: devid(0) speed(4) speed_str(wireless) vhci_hcd vhci_hcd.0: Device attached vhci_hcd: connection closed vhci_hcd: stop threads vhci_hcd: release socket vhci_hcd: disconnect device vhci_hcd: Failed attach request for unsupported USB speed: UNKNOWN vhci_hcd vhci_hcd.0: pdev(1) rhport(0) sockfd(4) vhci_hcd vhci_hcd.0: devid(0) speed(4) speed_str(wireless) vhci_hcd vhci_hcd.0: Device attached vhci_hcd: connection closed vhci_hcd: stop threads vhci_hcd: release socket vhci_hcd: disconnect device audit: type=1804 audit(1667090329.424:2): pid=10781 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.4" name="/root/syzkaller-testdir3868993341/syzkaller.VZIL1B/96/file0" dev="sda1" ino=14084 res=1 TCP: request_sock_TCP: Possible SYN flooding on port 2. Sending cookies. Check SNMP counters. netlink: 3 bytes leftover after parsing attributes in process `syz-executor.1'.