====================================================== WARNING: possible circular locking dependency detected 4.19.211-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.1/594 is trying to acquire lock: Started in network mode 00000000d96f8004 (&tree->tree_lock){+.+.}, at: hfsplus_file_truncate+0xde7/0x1040 fs/hfsplus/extents.c:595 but task is already holding lock: Own node identity fc, cluster identity 4711 000000003b87f9fd (&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 New replicast peer: fe80:0000:0000:0000:0000:0000:0000:0000 read_mapping_page include/linux/pagemap.h:402 [inline] __hfs_bnode_create+0x5b7/0xb60 fs/hfsplus/bnode.c:447 Enabled bearer , priority 10 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 Disabling bearer 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_setattr+0x1e7/0x310 fs/hfsplus/inode.c:263 notify_change+0x70b/0xfc0 fs/attr.c:334 do_truncate+0x134/0x1f0 fs/open.c:63 handle_truncate fs/namei.c:3009 [inline] do_last fs/namei.c:3427 [inline] path_openat+0x2308/0x2df0 fs/namei.c:3537 do_filp_open+0x18c/0x3f0 fs/namei.c:3567 do_sys_open+0x3b3/0x520 fs/open.c:1085 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 *** 3 locks held by syz-executor.1/594: #0: 00000000cf56b237 (sb_writers#21){.+.+}, at: sb_start_write include/linux/fs.h:1579 [inline] #0: 00000000cf56b237 (sb_writers#21){.+.+}, at: mnt_want_write+0x3a/0xb0 fs/namespace.c:360 #1: 00000000767b365f (&sb->s_type->i_mutex_key#25){+.+.}, at: inode_lock include/linux/fs.h:748 [inline] #1: 00000000767b365f (&sb->s_type->i_mutex_key#25){+.+.}, at: do_truncate+0x125/0x1f0 fs/open.c:61 #2: 000000003b87f9fd (&HFSPLUS_I(inode)->extents_lock){+.+.}, at: hfsplus_file_truncate+0x1e2/0x1040 fs/hfsplus/extents.c:576 stack backtrace: CPU: 1 PID: 594 Comm: syz-executor.1 Not tainted 4.19.211-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/12/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_setattr+0x1e7/0x310 fs/hfsplus/inode.c:263 notify_change+0x70b/0xfc0 fs/attr.c:334 do_truncate+0x134/0x1f0 fs/open.c:63 handle_truncate fs/namei.c:3009 [inline] do_last fs/namei.c:3427 [inline] path_openat+0x2308/0x2df0 fs/namei.c:3537 do_filp_open+0x18c/0x3f0 fs/namei.c:3567 do_sys_open+0x3b3/0x520 fs/open.c:1085 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe RIP: 0033:0x7fd702d4e0c9 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:00007fd7012c0168 EFLAGS: 00000246 ORIG_RAX: 0000000000000002 RAX: ffffffffffffffda RBX: 00007fd702e6df80 RCX: 00007fd702d4e0c9 RDX: 0000000000000000 RSI: 0000000000143242 RDI: 0000000020000000 RBP: 00007fd702da9ae9 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffe5f2e1c4f R14: 00007fd7012c0300 R15: 0000000000022000 hfsplus: unable to parse mount options New replicast peer: fe80:0000:0000:0000:0000:0000:0000:0000 Enabled bearer , priority 10 Disabling bearer IPVS: ftp: loaded support on port[0] = 21 New replicast peer: fe80:0000:0000:0000:0000:0000:0000:0000 Enabled bearer , priority 10 Disabling bearer UDF-fs: INFO Mounting volume 'LinuxUDF', timestamp 2022/11/22 14:59 (1000) team0: Device lo is loopback device. Loopback devices can't be added as a team port UDF-fs: warning (device loop1): udf_truncate_tail_extent: Too long extent after EOF in inode 1403: i_size: 241664 lbcount: 245760 extent 170+209920 team0: Device lo is loopback device. Loopback devices can't be added as a team port IPVS: ftp: loaded support on port[0] = 21 overlayfs: failed to resolve 'w5U)`)YFnA@T<3ڂ$rcnHwC" -8/': -2 overlayfs: failed to resolve 'w5U)`)YFnA@T<3ڂ$rcnHwC" -8/': -2 EXT4-fs error (device loop1): ext4_orphan_get:1256: comm syz-executor.1: bad orphan inode 34020 kauditd_printk_skb: 28 callbacks suppressed audit: type=1804 audit(1674822384.661:1221): pid=954 uid=0 auid=4294967295 ses=4294967295 subj==unconfined op=invalid_pcr cause=open_writers comm="syz-executor.0" name="/root/syzkaller-testdir3138437006/syzkaller.HmblbN/446/bus" dev="sda1" ino=14127 res=1 EXT4-fs (loop1): mounted filesystem without journal. Opts: ,errors=continue overlayfs: failed to resolve 'w5U)`)YFnA@T<3ڂ$rcnHwC" -8/': -2 audit: type=1804 audit(1674822385.161:1222): pid=1001 uid=0 auid=4294967295 ses=4294967295 subj==unconfined op=invalid_pcr cause=open_writers comm="syz-executor.0" name="/root/syzkaller-testdir3138437006/syzkaller.HmblbN/447/bus" dev="sda1" ino=14279 res=1 IPVS: ftp: loaded support on port[0] = 21 audit: type=1804 audit(1674822385.211:1223): pid=1001 uid=0 auid=4294967295 ses=4294967295 subj==unconfined op=invalid_pcr cause=ToMToU comm="syz-executor.0" name="/root/syzkaller-testdir3138437006/syzkaller.HmblbN/447/bus" dev="sda1" ino=14279 res=1 audit: type=1804 audit(1674822385.401:1224): pid=1036 uid=0 auid=4294967295 ses=4294967295 subj==unconfined op=invalid_pcr cause=open_writers comm="syz-executor.0" name="/root/syzkaller-testdir3138437006/syzkaller.HmblbN/448/bus" dev="sda1" ino=14196 res=1 audit: type=1804 audit(1674822385.481:1225): pid=1037 uid=0 auid=4294967295 ses=4294967295 subj==unconfined op=invalid_pcr cause=ToMToU comm="syz-executor.0" name="/root/syzkaller-testdir3138437006/syzkaller.HmblbN/448/bus" dev="sda1" ino=14196 res=1 ptrace attach of "/root/syz-executor.5 exec"[8138] was attempted by "/root/syz-executor.5 exec"[1106] ptrace attach of "/root/syz-executor.5 exec"[8138] was attempted by "/root/syz-executor.5 exec"[1106] ptrace attach of "/root/syz-executor.5 exec"[8138] was attempted by "/root/syz-executor.5 exec"[1120] ptrace attach of "/root/syz-executor.5 exec"[8138] was attempted by "/root/syz-executor.5 exec"[1120] ptrace attach of "/root/syz-executor.5 exec"[8138] was attempted by "/root/syz-executor.5 exec"[1158] ptrace attach of "/root/syz-executor.5 exec"[8138] was attempted by "/root/syz-executor.5 exec"[1158] ptrace attach of "/root/syz-executor.5 exec"[8138] was attempted by "/root/syz-executor.5 exec"[1179] IPVS: ftp: loaded support on port[0] = 21 IPVS: ftp: loaded support on port[0] = 21 IPVS: ftp: loaded support on port[0] = 21