ntfs: volume version 3.1. syz-executor.5 (11941): drop_caches: 1 ====================================================== WARNING: possible circular locking dependency detected 4.14.306-syzkaller #0 Not tainted ------------------------------------------------------ kworker/u4:2/25 is trying to acquire lock: (&rl->lock){++++}, at: [] ntfs_read_block fs/ntfs/aops.c:269 [inline] (&rl->lock){++++}, at: [] ntfs_readpage+0x1396/0x1ad0 fs/ntfs/aops.c:456 but task is already holding lock: (&ni->mrec_lock){+.+.}, at: [] map_mft_record+0x2b/0xbe0 fs/ntfs/mft.c:166 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&ni->mrec_lock){+.+.}: __mutex_lock_common kernel/locking/mutex.c:756 [inline] __mutex_lock+0xc4/0x1310 kernel/locking/mutex.c:893 map_mft_record+0x2b/0xbe0 fs/ntfs/mft.c:166 ntfs_truncate+0x1a6/0x22d0 fs/ntfs/inode.c:2415 ntfs_truncate_vfs fs/ntfs/inode.c:2895 [inline] ntfs_setattr+0x148/0x580 fs/ntfs/inode.c:2945 notify_change+0x56b/0xd10 fs/attr.c:315 do_truncate+0xff/0x1a0 fs/open.c:63 handle_truncate fs/namei.c:3010 [inline] do_last fs/namei.c:3437 [inline] path_openat+0x1dcc/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+0x5e/0xd3 -> #0 (&rl->lock){++++}: lock_acquire+0x170/0x3f0 kernel/locking/lockdep.c:3998 down_read+0x36/0x80 kernel/locking/rwsem.c:24 ntfs_read_block fs/ntfs/aops.c:269 [inline] ntfs_readpage+0x1396/0x1ad0 fs/ntfs/aops.c:456 do_read_cache_page+0x38e/0xc10 mm/filemap.c:2713 read_mapping_page include/linux/pagemap.h:398 [inline] ntfs_map_page fs/ntfs/aops.h:89 [inline] ntfs_sync_mft_mirror+0x1f4/0x1560 fs/ntfs/mft.c:490 write_mft_record_nolock+0xece/0x1240 fs/ntfs/mft.c:793 write_mft_record fs/ntfs/mft.h:109 [inline] __ntfs_write_inode+0x58d/0xcc0 fs/ntfs/inode.c:3084 write_inode fs/fs-writeback.c:1241 [inline] __writeback_single_inode+0x6a4/0x1010 fs/fs-writeback.c:1439 writeback_sb_inodes+0x48b/0xd30 fs/fs-writeback.c:1645 wb_writeback+0x243/0xb80 fs/fs-writeback.c:1820 wb_do_writeback fs/fs-writeback.c:1952 [inline] wb_workfn+0x2bd/0xf50 fs/fs-writeback.c:1988 process_one_work+0x793/0x14a0 kernel/workqueue.c:2117 worker_thread+0x5cc/0xff0 kernel/workqueue.c:2251 kthread+0x30d/0x420 kernel/kthread.c:232 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:406 other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&ni->mrec_lock); lock(&rl->lock); lock(&ni->mrec_lock); lock(&rl->lock); *** DEADLOCK *** 3 locks held by kworker/u4:2/25: #0: ("writeback"){+.+.}, at: [] process_one_work+0x6b0/0x14a0 kernel/workqueue.c:2088 #1: ((&(&wb->dwork)->work)){+.+.}, at: [] process_one_work+0x6e6/0x14a0 kernel/workqueue.c:2092 #2: (&ni->mrec_lock){+.+.}, at: [] map_mft_record+0x2b/0xbe0 fs/ntfs/mft.c:166 stack backtrace: CPU: 0 PID: 25 Comm: kworker/u4:2 Not tainted 4.14.306-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/21/2023 ntfs: volume version 3.1. Workqueue: writeback wb_workfn (flush-7:4) 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 ntfs: volume version 3.1. lock_acquire+0x170/0x3f0 kernel/locking/lockdep.c:3998 down_read+0x36/0x80 kernel/locking/rwsem.c:24 ntfs_read_block fs/ntfs/aops.c:269 [inline] ntfs_readpage+0x1396/0x1ad0 fs/ntfs/aops.c:456 do_read_cache_page+0x38e/0xc10 mm/filemap.c:2713 read_mapping_page include/linux/pagemap.h:398 [inline] ntfs_map_page fs/ntfs/aops.h:89 [inline] ntfs_sync_mft_mirror+0x1f4/0x1560 fs/ntfs/mft.c:490 write_mft_record_nolock+0xece/0x1240 fs/ntfs/mft.c:793 write_mft_record fs/ntfs/mft.h:109 [inline] __ntfs_write_inode+0x58d/0xcc0 fs/ntfs/inode.c:3084 write_inode fs/fs-writeback.c:1241 [inline] __writeback_single_inode+0x6a4/0x1010 fs/fs-writeback.c:1439 writeback_sb_inodes+0x48b/0xd30 fs/fs-writeback.c:1645 wb_writeback+0x243/0xb80 fs/fs-writeback.c:1820 wb_do_writeback fs/fs-writeback.c:1952 [inline] wb_workfn+0x2bd/0xf50 fs/fs-writeback.c:1988 process_one_work+0x793/0x14a0 kernel/workqueue.c:2117 worker_thread+0x5cc/0xff0 kernel/workqueue.c:2251 kthread+0x30d/0x420 kernel/kthread.c:232 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:406 EXT4-fs (loop1): mounting ext2 file system using the ext4 subsystem EXT4-fs (loop1): orphan cleanup on readonly fs EXT4-fs error (device loop1): ext4_validate_block_bitmap:405: comm syz-executor.1: bg 0: block 18: invalid block bitmap EXT4-fs error (device loop1) in ext4_free_blocks:5010: Corrupt filesystem EXT4-fs (loop1): 1 truncate cleaned up EXT4-fs (loop1): mounted filesystem without journal. Opts: ,errors=continue REISERFS (device loop3): found reiserfs format "3.5" with non-standard journal REISERFS (device loop3): using ordered data mode reiserfs: using flush barriers REISERFS (device loop3): journal params: device loop3, size 512, journal first block 18, max trans len 256, max batch 225, max commit age 30, max trans age 30 EXT4-fs (loop1): mounting ext2 file system using the ext4 subsystem REISERFS (device loop3): checking transaction log (loop3) REISERFS (device loop3): Using r5 hash to sort names REISERFS (device loop3): using 3.5.x disk format REISERFS (device loop3): Created .reiserfs_priv - reserved for xattr storage. EXT4-fs (loop1): orphan cleanup on readonly fs EXT4-fs error (device loop1): ext4_validate_block_bitmap:405: comm syz-executor.1: bg 0: block 18: invalid block bitmap EXT4-fs error (device loop1) in ext4_free_blocks:5010: Corrupt filesystem EXT4-fs (loop1): 1 truncate cleaned up REISERFS (device loop3): found reiserfs format "3.5" with non-standard journal REISERFS (device loop3): using ordered data mode reiserfs: using flush barriers REISERFS (device loop3): journal params: device loop3, size 512, journal first block 18, max trans len 256, max batch 225, max commit age 30, max trans age 30 REISERFS (device loop3): checking transaction log (loop3) REISERFS (device loop3): Using r5 hash to sort names REISERFS (device loop3): using 3.5.x disk format REISERFS (device loop3): Created .reiserfs_priv - reserved for xattr storage. EXT4-fs (loop1): mounted filesystem without journal. Opts: ,errors=continue syz-executor.4 (12010): drop_caches: 1 syz-executor.5 (12009): drop_caches: 1 REISERFS (device loop2): found reiserfs format "3.5" with non-standard journal REISERFS (device loop2): using ordered data mode reiserfs: using flush barriers REISERFS (device loop2): journal params: device loop2, size 512, journal first block 18, max trans len 256, max batch 225, max commit age 30, max trans age 30 REISERFS (device loop3): found reiserfs format "3.5" with non-standard journal REISERFS (device loop3): using ordered data mode REISERFS (device loop2): checking transaction log (loop2) reiserfs: using flush barriers REISERFS (device loop2): Using r5 hash to sort names REISERFS (device loop3): journal params: device loop3, size 512, journal first block 18, max trans len 256, max batch 225, max commit age 30, max trans age 30 EXT4-fs (loop1): mounting ext2 file system using the ext4 subsystem REISERFS (device loop2): using 3.5.x disk format REISERFS (device loop3): checking transaction log (loop3) REISERFS (device loop3): Using r5 hash to sort names REISERFS (device loop2): Created .reiserfs_priv - reserved for xattr storage. REISERFS (device loop3): using 3.5.x disk format EXT4-fs (loop1): orphan cleanup on readonly fs REISERFS (device loop3): Created .reiserfs_priv - reserved for xattr storage. EXT4-fs error (device loop1): ext4_validate_block_bitmap:405: comm syz-executor.1: bg 0: block 18: invalid block bitmap EXT4-fs error (device loop1) in ext4_free_blocks:5010: Corrupt filesystem EXT4-fs (loop1): 1 truncate cleaned up EXT4-fs (loop1): mounted filesystem without journal. Opts: ,errors=continue syz-executor.4 (12080): drop_caches: 1 syz-executor.5 (12082): drop_caches: 1 EXT4-fs (loop1): mounting ext2 file system using the ext4 subsystem REISERFS (device loop3): found reiserfs format "3.5" with non-standard journal REISERFS (device loop2): found reiserfs format "3.5" with non-standard journal REISERFS (device loop3): using ordered data mode REISERFS (device loop2): using ordered data mode EXT4-fs (loop1): orphan cleanup on readonly fs EXT4-fs error (device loop1): ext4_validate_block_bitmap:405: comm syz-executor.1: bg 0: block 18: invalid block bitmap EXT4-fs error (device loop1) in ext4_free_blocks:5010: Corrupt filesystem reiserfs: using flush barriers EXT4-fs (loop1): 1 truncate cleaned up EXT4-fs (loop1): mounted filesystem without journal. Opts: ,errors=continue reiserfs: using flush barriers REISERFS (device loop2): journal params: device loop2, size 512, journal first block 18, max trans len 256, max batch 225, max commit age 30, max trans age 30 REISERFS (device loop2): checking transaction log (loop2) REISERFS (device loop2): Using r5 hash to sort names REISERFS (device loop3): journal params: device loop3, size 512, journal first block 18, max trans len 256, max batch 225, max commit age 30, max trans age 30 REISERFS (device loop2): using 3.5.x disk format REISERFS (device loop2): Created .reiserfs_priv - reserved for xattr storage. REISERFS (device loop3): checking transaction log (loop3) EXT4-fs (loop1): mounting ext2 file system using the ext4 subsystem REISERFS (device loop3): Using r5 hash to sort names REISERFS (device loop3): using 3.5.x disk format EXT4-fs (loop1): orphan cleanup on readonly fs REISERFS (device loop3): Created .reiserfs_priv - reserved for xattr storage. EXT4-fs error (device loop1): ext4_validate_block_bitmap:405: comm syz-executor.1: bg 0: block 18: invalid block bitmap EXT4-fs error (device loop1) in ext4_free_blocks:5010: Corrupt filesystem EXT4-fs (loop1): 1 truncate cleaned up EXT4-fs (loop1): mounted filesystem without journal. Opts: ,errors=continue REISERFS (device loop2): found reiserfs format "3.5" with non-standard journal REISERFS (device loop2): using ordered data mode reiserfs: using flush barriers REISERFS (device loop2): journal params: device loop2, size 512, journal first block 18, max trans len 256, max batch 225, max commit age 30, max trans age 30 REISERFS (device loop2): checking transaction log (loop2) REISERFS (device loop2): Using r5 hash to sort names REISERFS (device loop2): using 3.5.x disk format REISERFS (device loop2): Created .reiserfs_priv - reserved for xattr storage. syz-executor.4 (12119): drop_caches: 1 syz-executor.5 (12137): drop_caches: 1 TCP: request_sock_TCP: Possible SYN flooding on port 2. Sending cookies. Check SNMP counters. TCP: request_sock_TCP: Possible SYN flooding on port 2. Sending cookies. Check SNMP counters. TCP: request_sock_TCP: Possible SYN flooding on port 2. Sending cookies. Check SNMP counters. EXT4-fs (loop1): mounting ext2 file system using the ext4 subsystem EXT4-fs (loop1): orphan cleanup on readonly fs EXT4-fs error (device loop1): ext4_validate_block_bitmap:405: comm syz-executor.1: bg 0: block 18: invalid block bitmap TCP: request_sock_TCP: Possible SYN flooding on port 2. Sending cookies. Check SNMP counters. TCP: request_sock_TCP: Possible SYN flooding on port 2. Sending cookies. Check SNMP counters. EXT4-fs error (device loop1) in ext4_free_blocks:5010: Corrupt filesystem BTRFS info (device loop4): using free space tree BTRFS info (device loop4): has skinny extents EXT4-fs (loop1): 1 truncate cleaned up EXT4-fs (loop1): mounted filesystem without journal. Opts: ,errors=continue TCP: request_sock_TCP: Possible SYN flooding on port 2. Sending cookies. Check SNMP counters. TCP: request_sock_TCP: Possible SYN flooding on port 2. Sending cookies. Check SNMP counters. TCP: request_sock_TCP: Possible SYN flooding on port 2. Sending cookies. Check SNMP counters. EXT4-fs (loop1): mounting ext2 file system using the ext4 subsystem TCP: request_sock_TCP: Possible SYN flooding on port 2. Sending cookies. Check SNMP counters. EXT4-fs (loop1): orphan cleanup on readonly fs EXT4-fs error (device loop1): ext4_validate_block_bitmap:405: comm syz-executor.1: bg 0: block 18: invalid block bitmap TCP: request_sock_TCP: Possible SYN flooding on port 2. Sending cookies. Check SNMP counters. EXT4-fs error (device loop1) in ext4_free_blocks:5010: Corrupt filesystem EXT4-fs (loop1): 1 truncate cleaned up EXT4-fs (loop1): mounted filesystem without journal. Opts: ,errors=continue BTRFS info (device loop5): using free space tree BTRFS info (device loop5): has skinny extents audit: type=1800 audit(1677079584.680:29): pid=12316 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.2" name="file0" dev="sda1" ino=13987 res=0 audit: type=1804 audit(1677079584.680:30): pid=12316 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.2" name="/root/syzkaller-testdir3979300416/syzkaller.FpH6TE/87/file0" dev="sda1" ino=13987 res=1 audit: type=1800 audit(1677079585.000:31): pid=12359 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.2" name="file0" dev="sda1" ino=13995 res=0 audit: type=1804 audit(1677079585.000:32): pid=12359 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.2" name="/root/syzkaller-testdir3979300416/syzkaller.FpH6TE/88/file0" dev="sda1" ino=13995 res=1 audit: type=1800 audit(1677079585.140:33): pid=12368 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.0" name="file0" dev="sda1" ino=13921 res=0 audit: type=1804 audit(1677079585.140:34): pid=12368 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.0" name="/root/syzkaller-testdir1280728152/syzkaller.H0HDKs/102/file0" dev="sda1" ino=13921 res=1 BTRFS info (device loop5): using free space tree BTRFS info (device loop5): has skinny extents audit: type=1800 audit(1677079585.220:35): pid=12377 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.2" name="file0" dev="sda1" ino=13995 res=0 audit: type=1804 audit(1677079585.220:36): pid=12377 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.2" name="/root/syzkaller-testdir3979300416/syzkaller.FpH6TE/89/file0" dev="sda1" ino=13995 res=1 audit: type=1800 audit(1677079585.350:37): pid=12386 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.0" name="file0" dev="sda1" ino=14035 res=0 audit: type=1804 audit(1677079585.350:38): pid=12386 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.0" name="/root/syzkaller-testdir1280728152/syzkaller.H0HDKs/103/file0" dev="sda1" ino=14035 res=1 XFS (loop1): Mounting V4 Filesystem XFS (loop1): Ending clean mount XFS (loop1): Unmounting Filesystem Protocol error: SET target dimension is over the limit! Protocol error: SET target dimension is over the limit! Protocol error: SET target dimension is over the limit! BTRFS info (device loop5): using free space tree Protocol error: SET target dimension is over the limit! BTRFS info (device loop5): has skinny extents XFS (loop1): Mounting V4 Filesystem XFS (loop1): Ending clean mount XFS (loop1): Unmounting Filesystem XFS (loop5): Mounting V4 Filesystem XFS (loop5): Ending clean mount XFS (loop2): Mounting V4 Filesystem XFS (loop2): Ending clean mount XFS (loop4): Mounting V4 Filesystem XFS (loop4): Ending clean mount XFS (loop2): Unmounting Filesystem XFS (loop5): Unmounting Filesystem XFS (loop3): Mounting V4 Filesystem XFS (loop3): Ending clean mount XFS (loop1): Mounting V4 Filesystem XFS (loop4): Unmounting Filesystem XFS (loop1): Ending clean mount XFS (loop2): Mounting V4 Filesystem XFS (loop3): Unmounting Filesystem XFS (loop2): Ending clean mount XFS (loop1): Unmounting Filesystem XFS (loop5): Mounting V4 Filesystem XFS (loop5): Ending clean mount XFS (loop4): Mounting V4 Filesystem XFS (loop2): Unmounting Filesystem XFS (loop4): Ending clean mount XFS (loop5): Unmounting Filesystem XFS (loop3): Mounting V4 Filesystem XFS (loop3): Ending clean mount XFS (loop4): Unmounting Filesystem XFS (loop1): Mounting V4 Filesystem XFS (loop1): Ending clean mount