loop1: rw=0, want=201326594, limit=1024 Buffer I/O error on dev loop1, logical block 100663296, async page read hfsplus: unable to mark blocks free: error -5 hfsplus: can't free extent ====================================================== WARNING: possible circular locking dependency detected 4.19.211-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.1/25762 is trying to acquire lock: 00000000522624a6 (&tree->tree_lock){+.+.}, at: hfsplus_file_truncate+0xde7/0x1040 fs/hfsplus/extents.c:595 but task is already holding lock: 000000000cdded47 (&HFSPLUS_I(inode)->extents_lock){+.+.}, at: hfsplus_file_truncate+0x1e2/0x1040 fs/hfsplus/extents.c:576 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&HFSPLUS_I(inode)->extents_lock){+.+.}: hfsplus_get_block+0x292/0x960 fs/hfsplus/extents.c:260 block_read_full_page+0x288/0xd10 fs/buffer.c:2259 do_read_cache_page+0x533/0x1170 mm/filemap.c:2828 read_mapping_page include/linux/pagemap.h:402 [inline] __hfs_bnode_create+0x5b7/0xb60 fs/hfsplus/bnode.c:447 hfsplus_bnode_find+0x2aa/0xb80 fs/hfsplus/bnode.c:497 hfsplus_brec_find+0x2af/0x500 fs/hfsplus/bfind.c:183 hfsplus_brec_read+0x28/0x120 fs/hfsplus/bfind.c:222 hfsplus_find_cat+0x1d0/0x480 fs/hfsplus/catalog.c:202 hfsplus_iget+0x400/0x790 fs/hfsplus/super.c:81 hfsplus_fill_super+0xc5f/0x19e0 fs/hfsplus/super.c:503 mount_bdev+0x2fc/0x3b0 fs/super.c:1158 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 (&tree->tree_lock){+.+.}: __mutex_lock_common kernel/locking/mutex.c:937 [inline] __mutex_lock+0xd7/0x1190 kernel/locking/mutex.c:1078 hfsplus_file_truncate+0xde7/0x1040 fs/hfsplus/extents.c:595 hfsplus_delete_inode+0x18d/0x220 fs/hfsplus/inode.c:419 hfsplus_unlink+0x595/0x820 fs/hfsplus/dir.c:405 hfsplus_rename+0xbe/0x200 fs/hfsplus/dir.c:545 vfs_rename+0x67e/0x1bc0 fs/namei.c:4479 do_renameat2+0xb59/0xc70 fs/namei.c:4629 __do_sys_rename fs/namei.c:4675 [inline] __se_sys_rename fs/namei.c:4673 [inline] __x64_sys_rename+0x5d/0x80 fs/namei.c:4673 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(&HFSPLUS_I(inode)->extents_lock); lock(&tree->tree_lock); lock(&HFSPLUS_I(inode)->extents_lock); lock(&tree->tree_lock); *** DEADLOCK *** 8 locks held by syz-executor.1/25762: #0: 000000007e460f35 (sb_writers#19){.+.+}, at: sb_start_write include/linux/fs.h:1579 [inline] #0: 000000007e460f35 (sb_writers#19){.+.+}, at: mnt_want_write+0x3a/0xb0 fs/namespace.c:360 #1: 000000001328dc9d (&type->s_vfs_rename_key#4){+.+.}, at: lock_rename+0x54/0x280 fs/namei.c:2867 #2: 00000000a54bb99f (&type->i_mutex_dir_key#11/1){+.+.}, at: inode_lock_nested include/linux/fs.h:783 [inline] #2: 00000000a54bb99f (&type->i_mutex_dir_key#11/1){+.+.}, at: lock_rename+0x132/0x280 fs/namei.c:2878 #3: 000000006214cfac (&type->i_mutex_dir_key#11/2){+.+.}, at: inode_lock_nested include/linux/fs.h:783 [inline] #3: 000000006214cfac (&type->i_mutex_dir_key#11/2){+.+.}, at: lock_rename+0x166/0x280 fs/namei.c:2879 #4: 000000002f7ff885 (&sb->s_type->i_mutex_key#25){+.+.}, at: inode_lock include/linux/fs.h:748 [inline] #4: 000000002f7ff885 (&sb->s_type->i_mutex_key#25){+.+.}, at: lock_two_nondirectories+0xec/0x110 fs/inode.c:1015 #5: 00000000df05091e (&sb->s_type->i_mutex_key#25/4){+.+.}, at: inode_lock_nested include/linux/fs.h:783 [inline] #5: 00000000df05091e (&sb->s_type->i_mutex_key#25/4){+.+.}, at: lock_two_nondirectories+0xd1/0x110 fs/inode.c:1017 #6: 00000000e9d0888b (&sbi->vh_mutex){+.+.}, at: hfsplus_unlink+0x140/0x820 fs/hfsplus/dir.c:370 #7: 000000000cdded47 (&HFSPLUS_I(inode)->extents_lock){+.+.}, at: hfsplus_file_truncate+0x1e2/0x1040 fs/hfsplus/extents.c:576 stack backtrace: CPU: 0 PID: 25762 Comm: syz-executor.1 Not tainted 4.19.211-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/16/2023 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 __mutex_lock_common kernel/locking/mutex.c:937 [inline] __mutex_lock+0xd7/0x1190 kernel/locking/mutex.c:1078 hfsplus_file_truncate+0xde7/0x1040 fs/hfsplus/extents.c:595 hfsplus_delete_inode+0x18d/0x220 fs/hfsplus/inode.c:419 hfsplus_unlink+0x595/0x820 fs/hfsplus/dir.c:405 hfsplus_rename+0xbe/0x200 fs/hfsplus/dir.c:545 vfs_rename+0x67e/0x1bc0 fs/namei.c:4479 do_renameat2+0xb59/0xc70 fs/namei.c:4629 __do_sys_rename fs/namei.c:4675 [inline] __se_sys_rename fs/namei.c:4673 [inline] __x64_sys_rename+0x5d/0x80 fs/namei.c:4673 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe RIP: 0033:0x7f52a84b50f9 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:00007f52a6a27168 EFLAGS: 00000246 ORIG_RAX: 0000000000000052 RAX: ffffffffffffffda RBX: 00007f52a85d4f80 RCX: 00007f52a84b50f9 RDX: 0000000000000000 RSI: 0000000020000140 RDI: 0000000020000000 RBP: 00007f52a8510ae9 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffce91aaf8f R14: 00007f52a6a27300 R15: 0000000000022000 EXT4-fs (loop3): Unrecognized mount option "VF4}H" or missing value attempt to access beyond end of device loop1: rw=0, want=201326594, limit=1024 Buffer I/O error on dev loop1, logical block 100663296, async page read hfsplus: unable to mark blocks free: error -5 hfsplus: can't free extent EXT4-fs (loop3): Unrecognized mount option "VF4}H" or missing value EXT4-fs (loop3): Unrecognized mount option "VF4}H" or missing value attempt to access beyond end of device loop1: rw=0, want=201326594, limit=1024 Buffer I/O error on dev loop1, logical block 100663296, async page read nf_conntrack: default automatic helper assignment has been turned off for security reasons and CT-based firewall rule not found. Use the iptables CT target to attach helpers instead. hfsplus: unable to mark blocks free: error -5 hfsplus: can't free extent ntfs: (device loop2): parse_options(): Invalid errors option argument: conMZJ12$}tinue xt_CT: You must specify a L4 protocol and not use inversions on it ntfs: (device loop2): parse_options(): Invalid errors option argument: conMZJ12$}tinue audit: type=1804 audit(1677853687.326:304): pid=26033 uid=0 auid=4294967295 ses=4294967295 subj==unconfined op=invalid_pcr cause=open_writers comm="syz-executor.5" name="/root/syzkaller-testdir2022513268/syzkaller.U7qOdT/618/bus" dev="sda1" ino=14977 res=1 audit: type=1804 audit(1677853687.356:305): pid=26033 uid=0 auid=4294967295 ses=4294967295 subj==unconfined op=invalid_pcr cause=ToMToU comm="syz-executor.5" name="/root/syzkaller-testdir2022513268/syzkaller.U7qOdT/618/bus" dev="sda1" ino=14977 res=1 audit: type=1804 audit(1677853687.356:306): pid=26033 uid=0 auid=4294967295 ses=4294967295 subj==unconfined op=invalid_pcr cause=open_writers comm="syz-executor.5" name="/root/syzkaller-testdir2022513268/syzkaller.U7qOdT/618/bus" dev="sda1" ino=14977 res=1 audit: type=1804 audit(1677853687.446:307): pid=26033 uid=0 auid=4294967295 ses=4294967295 subj==unconfined op=invalid_pcr cause=ToMToU comm="syz-executor.5" name="/root/syzkaller-testdir2022513268/syzkaller.U7qOdT/618/bus" dev="sda1" ino=14977 res=1 ntfs: (device loop2): parse_options(): Invalid errors option argument: conMZJ12$}tinue xt_CT: You must specify a L4 protocol and not use inversions on it audit: type=1804 audit(1677853687.766:308): pid=26104 uid=0 auid=4294967295 ses=4294967295 subj==unconfined op=invalid_pcr cause=open_writers comm="syz-executor.5" name="/root/syzkaller-testdir2022513268/syzkaller.U7qOdT/619/bus" dev="sda1" ino=15416 res=1 audit: type=1804 audit(1677853687.876:309): pid=26125 uid=0 auid=4294967295 ses=4294967295 subj==unconfined op=invalid_pcr cause=open_writers comm="syz-executor.5" name="/root/syzkaller-testdir2022513268/syzkaller.U7qOdT/620/bus" dev="sda1" ino=14065 res=1 audit: type=1804 audit(1677853687.886:310): pid=26122 uid=0 auid=4294967295 ses=4294967295 subj==unconfined op=invalid_pcr cause=ToMToU comm="syz-executor.5" name="/root/syzkaller-testdir2022513268/syzkaller.U7qOdT/620/bus" dev="sda1" ino=14065 res=1 XFS (loop2): DAX enabled. Warning: EXPERIMENTAL, use at your own risk XFS (loop2): DAX unsupported by block device. Turning off DAX. XFS (loop2): Mounting V4 Filesystem XFS (loop2): Ending clean mount XFS (loop2): Quotacheck needed: Please wait. XFS (loop2): Quotacheck: Done. xt_CT: You must specify a L4 protocol and not use inversions on it xt_CT: You must specify a L4 protocol and not use inversions on it xt_CT: You must specify a L4 protocol and not use inversions on it XFS (loop2): Unmounting Filesystem xt_CT: You must specify a L4 protocol and not use inversions on it nf_conntrack: default automatic helper assignment has been turned off for security reasons and CT-based firewall rule not found. Use the iptables CT target to attach helpers instead. xt_CT: You must specify a L4 protocol and not use inversions on it xt_CT: You must specify a L4 protocol and not use inversions on it xt_CT: You must specify a L4 protocol and not use inversions on it xt_CT: You must specify a L4 protocol and not use inversions on it xt_ct_set_helper: 3 callbacks suppressed xt_CT: You must specify a L4 protocol and not use inversions on it xt_CT: You must specify a L4 protocol and not use inversions on it xt_CT: You must specify a L4 protocol and not use inversions on it xt_CT: You must specify a L4 protocol and not use inversions on it xt_CT: You must specify a L4 protocol and not use inversions on it xt_CT: You must specify a L4 protocol and not use inversions on it xt_CT: You must specify a L4 protocol and not use inversions on it