ntfs: volume version 3.1. ====================================================== WARNING: possible circular locking dependency detected 4.14.301-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.2/11264 is trying to acquire lock: (&ni->mrec_lock){+.+.}, at: [] map_mft_record+0x2b/0xbe0 fs/ntfs/mft.c:166 but task is already holding lock: (&rl->lock){++++}, at: [] ntfs_truncate+0x162/0x22d0 fs/ntfs/inode.c:2410 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&rl->lock){++++}: 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 -> #0 (&ni->mrec_lock){+.+.}: lock_acquire+0x170/0x3f0 kernel/locking/lockdep.c:3998 __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 other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&rl->lock); lock(&ni->mrec_lock); lock(&rl->lock); lock(&ni->mrec_lock); *** DEADLOCK *** 3 locks held by syz-executor.2/11264: #0: (sb_writers#18){.+.+}, at: [] sb_start_write include/linux/fs.h:1551 [inline] #0: (sb_writers#18){.+.+}, at: [] mnt_want_write+0x3a/0xb0 fs/namespace.c:386 #1: (&sb->s_type->i_mutex_key#26){+.+.}, at: [] inode_lock include/linux/fs.h:719 [inline] #1: (&sb->s_type->i_mutex_key#26){+.+.}, at: [] do_truncate+0xf0/0x1a0 fs/open.c:61 #2: (&rl->lock){++++}, at: [] ntfs_truncate+0x162/0x22d0 fs/ntfs/inode.c:2410 stack backtrace: CPU: 1 PID: 11264 Comm: syz-executor.2 Not tainted 4.14.301-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/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 __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 RIP: 0033:0x7f11171bf0d9 RSP: 002b:00007f1115731168 EFLAGS: 00000246 ORIG_RAX: 0000000000000055 RAX: ffffffffffffffda RBX: 00007f11172def80 RCX: 00007f11171bf0d9 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000020000080 RBP: 00007f111721aae9 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffeae756fbf R14: 00007f1115731300 R15: 0000000000022000 UDF-fs: INFO Mounting volume 'LinuxUDF', timestamp 2022/11/22 14:59 (1000) audit: type=1804 audit(1670972449.191:55): pid=11260 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.5" name="/root/syzkaller-testdir501102005/syzkaller.W9g8Wd/57/bus" dev="sda1" ino=14218 res=1 audit: type=1804 audit(1670972449.191:56): pid=11260 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.5" name="/root/syzkaller-testdir501102005/syzkaller.W9g8Wd/57/bus" dev="sda1" ino=14218 res=1 audit: type=1804 audit(1670972449.501:57): pid=11280 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.1" name="/root/syzkaller-testdir3951500998/syzkaller.v8wmSf/66/bus" dev="sda1" ino=14206 res=1 audit: type=1804 audit(1670972449.501:58): pid=11280 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.1" name="/root/syzkaller-testdir3951500998/syzkaller.v8wmSf/66/bus" dev="sda1" ino=14206 res=1 print_req_error: I/O error, dev loop4, sector 0 print_req_error: I/O error, dev loop4, sector 0 Buffer I/O error on dev loop4, logical block 0, async page read UDF-fs: INFO Mounting volume 'LinuxUDF', timestamp 2022/11/22 14:59 (1000) audit: type=1804 audit(1670972449.781:59): pid=11295 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.5" name="/root/syzkaller-testdir501102005/syzkaller.W9g8Wd/58/bus" dev="sda1" ino=14218 res=1 UDF-fs: INFO Mounting volume 'LinuxUDF', timestamp 2022/11/22 14:59 (1000) ntfs: volume version 3.1. ntfs: volume version 3.1. ISO 9660 Extensions: Microsoft Joliet Level 3 ISOFS: changing to secondary root ISO 9660 Extensions: Microsoft Joliet Level 3 ISOFS: changing to secondary root ntfs: volume version 3.1. ISO 9660 Extensions: Microsoft Joliet Level 3 ntfs: volume version 3.1. ISOFS: changing to secondary root ntfs: volume version 3.1. unregister_netdevice: waiting for ip6gre0 to become free. Usage count = -1 ISO 9660 Extensions: Microsoft Joliet Level 3 ISOFS: changing to secondary root ISO 9660 Extensions: Microsoft Joliet Level 3 ISOFS: changing to secondary root ISO 9660 Extensions: Microsoft Joliet Level 3 ISOFS: changing to secondary root ISO 9660 Extensions: Microsoft Joliet Level 3 ISOFS: changing to secondary root ntfs: volume version 3.1. EXT4-fs (loop5): couldn't mount RDWR because of unsupported optional features (8000) BTRFS: device fsid 24c7a497-3402-47dd-bef8-82358f5f30e0 devid 1 transid 8 /dev/loop0 BTRFS info (device loop0): enabling inode map caching BTRFS warning (device loop0): excessive commit interval 622039222 BTRFS info (device loop0): force zlib compression BTRFS info (device loop0): using free space tree BTRFS info (device loop0): has skinny extents ntfs: volume version 3.1. BTRFS info (device loop0): enabling inode map caching BTRFS warning (device loop0): excessive commit interval 622039222 BTRFS info (device loop0): force zlib compression BTRFS info (device loop0): using free space tree BTRFS info (device loop0): has skinny extents Bearer rejected, not supported in standalone mode Bearer rejected, not supported in standalone mode