====================================================== WARNING: possible circular locking dependency detected 4.19.211-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.5/12969 is trying to acquire lock: 0000000020ce2d7c (&tree->tree_lock#2){+.+.}, at: hfsplus_file_truncate+0xde7/0x1040 fs/hfsplus/extents.c:595 but task is already holding lock: 00000000ccd7af93 (&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_file_extend+0x1bb/0xf40 fs/hfsplus/extents.c:457 hfsplus_bmap_reserve+0x298/0x440 fs/hfsplus/btree.c:357 hfsplus_create_cat+0x1e3/0x1210 fs/hfsplus/catalog.c:272 hfsplus_fill_super+0x14a8/0x19e0 fs/hfsplus/super.c:560 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#2){+.+.}: __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_file_release+0xeb/0x210 fs/hfsplus/inode.c:233 __fput+0x2ce/0x890 fs/file_table.c:278 task_work_run+0x148/0x1c0 kernel/task_work.c:113 tracehook_notify_resume include/linux/tracehook.h:193 [inline] exit_to_usermode_loop+0x251/0x2a0 arch/x86/entry/common.c:167 prepare_exit_to_usermode arch/x86/entry/common.c:198 [inline] syscall_return_slowpath arch/x86/entry/common.c:271 [inline] do_syscall_64+0x538/0x620 arch/x86/entry/common.c:296 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#2); lock(&HFSPLUS_I(inode)->extents_lock); lock(&tree->tree_lock#2); *** DEADLOCK *** 2 locks held by syz-executor.5/12969: #0: 000000005b213023 (&sb->s_type->i_mutex_key#23){+.+.}, at: inode_lock include/linux/fs.h:748 [inline] #0: 000000005b213023 (&sb->s_type->i_mutex_key#23){+.+.}, at: hfsplus_file_release+0xe3/0x210 fs/hfsplus/inode.c:232 #1: 00000000ccd7af93 (&HFSPLUS_I(inode)->extents_lock){+.+.}, at: hfsplus_file_truncate+0x1e2/0x1040 fs/hfsplus/extents.c:576 stack backtrace: CPU: 0 PID: 12969 Comm: syz-executor.5 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_file_release+0xeb/0x210 fs/hfsplus/inode.c:233 __fput+0x2ce/0x890 fs/file_table.c:278 task_work_run+0x148/0x1c0 kernel/task_work.c:113 tracehook_notify_resume include/linux/tracehook.h:193 [inline] exit_to_usermode_loop+0x251/0x2a0 arch/x86/entry/common.c:167 prepare_exit_to_usermode arch/x86/entry/common.c:198 [inline] syscall_return_slowpath arch/x86/entry/common.c:271 [inline] do_syscall_64+0x538/0x620 arch/x86/entry/common.c:296 entry_SYSCALL_64_after_hwframe+0x49/0xbe RIP: 0033:0x7f78fe1cdf7b Code: 0f 05 48 3d 00 f0 ff ff 77 45 c3 0f 1f 40 00 48 83 ec 18 89 7c 24 0c e8 63 fc ff ff 8b 7c 24 0c 41 89 c0 b8 03 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 35 44 89 c7 89 44 24 0c e8 a1 fc ff ff 8b 44 RSP: 002b:00007fff1bfc46c0 EFLAGS: 00000293 ORIG_RAX: 0000000000000003 RAX: 0000000000000000 RBX: 0000000000000005 RCX: 00007f78fe1cdf7b RDX: 00007f78fdd91168 RSI: ffffffffffffffff RDI: 0000000000000004 RBP: 00007f78fe33d980 R08: 0000000000000000 R09: 00007f78fdd90000 R10: 00007f78fdd91170 R11: 0000000000000293 R12: 00000000000b9182 R13: 00007fff1bfc47c0 R14: 00007f78fe33bf80 R15: 0000000000000032 IPVS: ftp: loaded support on port[0] = 21 netlink: 'syz-executor.2': attribute type 4 has an invalid length. print_req_error: 240 callbacks suppressed print_req_error: I/O error, dev loop1, sector 2056 print_req_error: I/O error, dev loop1, sector 32512 print_req_error: I/O error, dev loop1, sector 32512 buffer_io_error: 206 callbacks suppressed Buffer I/O error on dev loop1p2, logical block 32512, async page read print_req_error: I/O error, dev loop1, sector 32513 Buffer I/O error on dev loop1p2, logical block 32513, async page read print_req_error: I/O error, dev loop1, sector 3072 print_req_error: I/O error, dev loop1, sector 32514 Buffer I/O error on dev loop1p2, logical block 32514, async page read print_req_error: I/O error, dev loop1, sector 32515 Buffer I/O error on dev loop1p2, logical block 32515, async page read print_req_error: I/O error, dev loop1, sector 32516 Buffer I/O error on dev loop1p2, logical block 32516, async page read print_req_error: I/O error, dev loop1, sector 32517 Buffer I/O error on dev loop1p2, logical block 32517, async page read print_req_error: I/O error, dev loop1, sector 32518 Buffer I/O error on dev loop1p2, logical block 32518, async page read Buffer I/O error on dev loop1p2, logical block 32519, async page read Buffer I/O error on dev loop1p1, logical block 1, async page read Buffer I/O error on dev loop1p3, logical block 0, async page read IPVS: ftp: loaded support on port[0] = 21 netlink: 'syz-executor.2': attribute type 4 has an invalid length. IPVS: ftp: loaded support on port[0] = 21 netlink: 'syz-executor.5': attribute type 4 has an invalid length. IPVS: ftp: loaded support on port[0] = 21 netlink: 'syz-executor.2': attribute type 4 has an invalid length. IPVS: ftp: loaded support on port[0] = 21 netlink: 'syz-executor.5': attribute type 4 has an invalid length. IPVS: ftp: loaded support on port[0] = 21 netlink: 'syz-executor.0': attribute type 4 has an invalid length. IPVS: ftp: loaded support on port[0] = 21 netlink: 'syz-executor.5': attribute type 4 has an invalid length. IPVS: ftp: loaded support on port[0] = 21 netlink: 'syz-executor.5': attribute type 4 has an invalid length. IPVS: ftp: loaded support on port[0] = 21 netlink: 'syz-executor.5': attribute type 4 has an invalid length. print_req_error: 284 callbacks suppressed print_req_error: I/O error, dev loop1, sector 2056 print_req_error: I/O error, dev loop1, sector 32512 print_req_error: I/O error, dev loop1, sector 3072 print_req_error: I/O error, dev loop1, sector 32512 buffer_io_error: 242 callbacks suppressed Buffer I/O error on dev loop1p2, logical block 32512, async page read print_req_error: I/O error, dev loop1, sector 32513 Buffer I/O error on dev loop1p2, logical block 32513, async page read print_req_error: I/O error, dev loop1, sector 32514 Buffer I/O error on dev loop1p2, logical block 32514, async page read print_req_error: I/O error, dev loop1, sector 32515 Buffer I/O error on dev loop1p2, logical block 32515, async page read print_req_error: I/O error, dev loop1, sector 3072 Buffer I/O error on dev loop1p3, logical block 0, async page read print_req_error: I/O error, dev loop1, sector 2056 Buffer I/O error on dev loop1p1, logical block 1, async page read print_req_error: I/O error, dev loop1, sector 3072 Buffer I/O error on dev loop1p3, logical block 0, async page read Buffer I/O error on dev loop1p3, logical block 0, async page read Buffer I/O error on dev loop1p3, logical block 0, async page read Buffer I/O error on dev loop1p2, logical block 32516, async page read IPVS: ftp: loaded support on port[0] = 21 netlink: 'syz-executor.5': attribute type 4 has an invalid length. overlayfs: failed to resolve './file0': -2 IPVS: ftp: loaded support on port[0] = 21 netlink: 'syz-executor.5': attribute type 4 has an invalid length. IPVS: ftp: loaded support on port[0] = 21 netlink: 'syz-executor.5': attribute type 4 has an invalid length.