syz-executor.0 (10109): drop_caches: 1
======================================================
WARNING: possible circular locking dependency detected
4.14.295-syzkaller #0 Not tainted
------------------------------------------------------
kworker/u4:2/35 is trying to acquire lock:
(&rl->lock){++++}, at: [<ffffffff82100e76>] ntfs_read_block fs/ntfs/aops.c:269 [inline]
(&rl->lock){++++}, at: [<ffffffff82100e76>] ntfs_readpage+0x1396/0x1ad0 fs/ntfs/aops.c:456
but task is already holding lock:
(&ni->mrec_lock){+.+.}, at: [<ffffffff8213be7b>] 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:2408
ntfs_truncate_vfs fs/ntfs/inode.c:2888 [inline]
ntfs_setattr+0x148/0x580 fs/ntfs/inode.c:2938
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+0x46/0xbb
-> #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:3077
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:404
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/35:
#0: ("writeback"){+.+.}, at: [<ffffffff81364eb0>] process_one_work+0x6b0/0x14a0 kernel/workqueue.c:2088
#1: ((&(&wb->dwork)->work)){+.+.}, at: [<ffffffff81364ee6>] process_one_work+0x6e6/0x14a0 kernel/workqueue.c:2092
#2: (&ni->mrec_lock){+.+.}, at: [<ffffffff8213be7b>] map_mft_record+0x2b/0xbe0 fs/ntfs/mft.c:166
stack backtrace:
CPU: 0 PID: 35 Comm: kworker/u4:2 Not tainted 4.14.295-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/11/2022
Workqueue: writeback wb_workfn (flush-7:1)
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
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:3077
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:404
SQUASHFS error: squashfs_read_data failed to read block 0x12a
SQUASHFS error: Unable to read metadata cache entry [12a]
SQUASHFS error: Unable to read inode 0x4000000910026
syz-executor.0 (10109): drop_caches: 1
print_req_error: I/O error, dev loop5, sector 0
unregister_netdevice: waiting for ip6gre0 to become free. Usage count = -1
sp0: Synchronizing with TNC
input: syz1 as /devices/virtual/input/input5
sp0: Synchronizing with TNC
sp0: Synchronizing with TNC
sp0: Synchronizing with TNC
encrypted_key: insufficient parameters specified
EXT4-fs (loop2): mounting ext2 file system using the ext4 subsystem
EXT4-fs warning (device loop2): ext4_update_dynamic_rev:793: updating to rev 1 because of new feature flag, running e2fsck is recommended
EXT4-fs (loop2): mounted filesystem without journal. Opts: ,errors=continue
audit: type=1800 audit(1666776024.771:7): pid=10313 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.2" name="file0" dev="loop2" ino=17 res=0
audit: type=1804 audit(1666776024.771:8): pid=10313 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.2" name="/root/syzkaller-testdir2788077321/syzkaller.8EsT2b/29/file0/file0" dev="loop2" ino=17 res=1
audit: type=1804 audit(1666776024.801:9): pid=10313 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="ToMToU" comm="syz-executor.2" name="/root/syzkaller-testdir2788077321/syzkaller.8EsT2b/29/file0/file0" dev="loop2" ino=17 res=1
EXT4-fs (loop2): mounting ext2 file system using the ext4 subsystem
EXT4-fs warning (device loop2): ext4_update_dynamic_rev:793: updating to rev 1 because of new feature flag, running e2fsck is recommended
EXT4-fs (loop2): mounted filesystem without journal. Opts: ,errors=continue
EXT4-fs (loop2): mounting ext2 file system using the ext4 subsystem
EXT4-fs warning (device loop2): ext4_update_dynamic_rev:793: updating to rev 1 because of new feature flag, running e2fsck is recommended
EXT4-fs (loop2): mounted filesystem without journal. Opts: ,errors=continue
audit: type=1800 audit(1666776025.651:10): pid=10390 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.2" name="file0" dev="loop2" ino=17 res=0
audit: type=1804 audit(1666776025.671:11): pid=10390 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.2" name="/root/syzkaller-testdir2788077321/syzkaller.8EsT2b/31/file0/file0" dev="loop2" ino=17 res=1
audit: type=1804 audit(1666776025.751:12): pid=10390 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="ToMToU" comm="syz-executor.2" name="/root/syzkaller-testdir2788077321/syzkaller.8EsT2b/31/file0/file0" dev="loop2" ino=17 res=1
EXT4-fs (loop2): mounting ext2 file system using the ext4 subsystem
EXT4-fs warning (device loop2): ext4_update_dynamic_rev:793: updating to rev 1 because of new feature flag, running e2fsck is recommended
hrtimer: interrupt took 16368 ns
EXT4-fs (loop2): mounted filesystem without journal. Opts: ,errors=continue
audit: type=1800 audit(1666776025.921:13): pid=10408 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor.2" name="file0" dev="loop2" ino=17 res=0
audit: type=1804 audit(1666776025.921:14): pid=10408 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.2" name="/root/syzkaller-testdir2788077321/syzkaller.8EsT2b/32/file0/file0" dev="loop2" ino=17 res=1
audit: type=1804 audit(1666776025.981:15): pid=10408 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="ToMToU" comm="syz-executor.2" name="/root/syzkaller-testdir2788077321/syzkaller.8EsT2b/32/file0/file0" dev="loop2" ino=17 res=1
BTRFS error (device loop2): unsupported checksum algorithm 1
BTRFS error (device loop2): superblock checksum mismatch
BTRFS error (device loop2): open_ctree failed
BTRFS error (device loop2): unsupported checksum algorithm 1
BTRFS error (device loop2): superblock checksum mismatch
BTRFS error (device loop2): open_ctree failed
BTRFS error (device loop2): unsupported checksum algorithm 1
BTRFS error (device loop2): superblock checksum mismatch
BTRFS error (device loop2): open_ctree failed
BTRFS error (device loop2): unsupported checksum algorithm 1
BTRFS error (device loop2): superblock checksum mismatch
input: syz1 as /devices/virtual/input/input6
BTRFS error (device loop2): open_ctree failed
BTRFS error (device loop3): unsupported checksum algorithm 1
BTRFS error (device loop3): superblock checksum mismatch
BTRFS error (device loop3): open_ctree failed
BTRFS error (device loop2): unsupported checksum algorithm 1
BTRFS error (device loop2): superblock checksum mismatch
BTRFS error (device loop2): open_ctree failed
BTRFS error (device loop3): unsupported checksum algorithm 1
BTRFS error (device loop3): superblock checksum mismatch
BTRFS error (device loop3): open_ctree failed
netlink: 12 bytes leftover after parsing attributes in process `syz-executor.3'.
device bond1 entered promiscuous mode
IPv6: ADDRCONF(NETDEV_UP): bond1: link is not ready
8021q: adding VLAN 0 to HW filter on device bond1
ntfs: volume version 3.1.