block nbd2: Device being setup by another task hfsplus: can't free extent ====================================================== WARNING: possible circular locking dependency detected 4.19.211-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.0/18409 is trying to acquire lock: 00000000b76368e1 (&tree->tree_lock){+.+.}, at: hfsplus_file_truncate+0xde7/0x1040 fs/hfsplus/extents.c:595 but task is already holding lock: 00000000b665acab (&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){+.+.}: __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.0/18409: #0: 00000000271f4321 (sb_writers#19){.+.+}, at: sb_start_write include/linux/fs.h:1579 [inline] #0: 00000000271f4321 (sb_writers#19){.+.+}, at: mnt_want_write+0x3a/0xb0 fs/namespace.c:360 #1: 00000000c8740b28 (&type->s_vfs_rename_key){+.+.}, at: lock_rename+0x54/0x280 fs/namei.c:2867 #2: 00000000f88e3df7 (&type->i_mutex_dir_key#12/1){+.+.}, at: inode_lock_nested include/linux/fs.h:783 [inline] #2: 00000000f88e3df7 (&type->i_mutex_dir_key#12/1){+.+.}, at: lock_rename+0x132/0x280 fs/namei.c:2878 #3: 000000008bf70c08 (&type->i_mutex_dir_key#12/2){+.+.}, at: inode_lock_nested include/linux/fs.h:783 [inline] #3: 000000008bf70c08 (&type->i_mutex_dir_key#12/2){+.+.}, at: lock_rename+0x166/0x280 fs/namei.c:2879 #4: 00000000aec614f4 (&sb->s_type->i_mutex_key#25){+.+.}, at: inode_lock include/linux/fs.h:748 [inline] #4: 00000000aec614f4 (&sb->s_type->i_mutex_key#25){+.+.}, at: lock_two_nondirectories+0xec/0x110 fs/inode.c:1015 #5: 000000004712317c (&sb->s_type->i_mutex_key#25/4){+.+.}, at: inode_lock_nested include/linux/fs.h:783 [inline] #5: 000000004712317c (&sb->s_type->i_mutex_key#25/4){+.+.}, at: lock_two_nondirectories+0xd1/0x110 fs/inode.c:1017 #6: 00000000f97bab5c (&sbi->vh_mutex){+.+.}, at: hfsplus_unlink+0x140/0x820 fs/hfsplus/dir.c:370 #7: 00000000b665acab (&HFSPLUS_I(inode)->extents_lock){+.+.}, at: hfsplus_file_truncate+0x1e2/0x1040 fs/hfsplus/extents.c:576 stack backtrace: CPU: 0 PID: 18409 Comm: syz-executor.0 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_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:0x7fc944c850c9 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:00007fc9431f7168 EFLAGS: 00000246 ORIG_RAX: 0000000000000052 RAX: ffffffffffffffda RBX: 00007fc944da4f80 RCX: 00007fc944c850c9 RDX: 0000000000000000 RSI: 0000000020000140 RDI: 0000000020000000 RBP: 00007fc944ce0ae9 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffee5f74d3f R14: 00007fc9431f7300 R15: 0000000000022000 print_req_error: 339 callbacks suppressed print_req_error: I/O error, dev loop3, sector 58 print_req_error: I/O error, dev loop3, sector 108 print_req_error: I/O error, dev loop3, sector 1008 print_req_error: I/O error, dev loop3, sector 58 buffer_io_error: 303 callbacks suppressed Buffer I/O error on dev loop3p2, logical block 8, async page read print_req_error: I/O error, dev loop3, sector 59 Buffer I/O error on dev loop3p2, logical block 9, async page read print_req_error: I/O error, dev loop3, sector 60 Buffer I/O error on dev loop3p2, logical block 10, async page read print_req_error: I/O error, dev loop3, sector 108 Buffer I/O error on dev loop3p1, logical block 8, async page read print_req_error: I/O error, dev loop3, sector 109 Buffer I/O error on dev loop3p1, logical block 9, async page read print_req_error: I/O error, dev loop3, sector 110 Buffer I/O error on dev loop3p1, logical block 10, async page read print_req_error: I/O error, dev loop3, sector 111 Buffer I/O error on dev loop3p1, logical block 11, async page read Buffer I/O error on dev loop3p1, logical block 12, async page read Buffer I/O error on dev loop3p1, logical block 13, async page read Buffer I/O error on dev loop3p1, logical block 14, async page read netlink: 16 bytes leftover after parsing attributes in process `syz-executor.1'. F2FS-fs (loop3): Invalid log blocks per segment (11337737) F2FS-fs (loop3): Can't find valid F2FS filesystem in 1th superblock F2FS-fs (loop3): Found nat_bits in checkpoint F2FS-fs (loop3): Cannot turn on quotas: -2 on 2 F2FS-fs (loop3): Mounted with checkpoint version = 48b305e5 IPVS: ftp: loaded support on port[0] = 21 netlink: 24 bytes leftover after parsing attributes in process `syz-executor.0'. attempt to access beyond end of device loop0: rw=0, want=201326594, limit=1024 hfsplus: unable to mark blocks free: error -5 hfsplus: can't free extent hfsplus: invalid secondary volume header hfsplus: unable to find HFS+ superblock F2FS-fs (loop3): Invalid log blocks per segment (11337737) F2FS-fs (loop3): Can't find valid F2FS filesystem in 1th superblock F2FS-fs (loop3): Found nat_bits in checkpoint F2FS-fs (loop5): Invalid log blocks per segment (11337737) F2FS-fs (loop5): Can't find valid F2FS filesystem in 1th superblock netlink: 80 bytes leftover after parsing attributes in process `syz-executor.0'. IPVS: ftp: loaded support on port[0] = 21 netlink: 16 bytes leftover after parsing attributes in process `syz-executor.1'. print_req_error: 125 callbacks suppressed print_req_error: I/O error, dev loop3, sector 108 print_req_error: I/O error, dev loop3, sector 58 print_req_error: I/O error, dev loop3, sector 108 buffer_io_error: 111 callbacks suppressed Buffer I/O error on dev loop3p1, logical block 8, async page read print_req_error: I/O error, dev loop3, sector 1008 print_req_error: I/O error, dev loop3, sector 109 Buffer I/O error on dev loop3p1, logical block 9, async page read print_req_error: I/O error, dev loop3, sector 58 Buffer I/O error on dev loop3p2, logical block 8, async page read print_req_error: I/O error, dev loop3, sector 59 Buffer I/O error on dev loop3p2, logical block 9, async page read print_req_error: I/O error, dev loop3, sector 60 Buffer I/O error on dev loop3p2, logical block 10, async page read print_req_error: I/O error, dev loop3, sector 61 Buffer I/O error on dev loop3p2, logical block 11, async page read print_req_error: I/O error, dev loop3, sector 62 Buffer I/O error on dev loop3p2, logical block 12, async page read Buffer I/O error on dev loop3p2, logical block 13, async page read Buffer I/O error on dev loop3p2, logical block 14, async page read Buffer I/O error on dev loop3p2, logical block 15, async page read audit: type=1800 audit(1674811677.579:19): pid=18853 uid=0 auid=4294967295 ses=4294967295 subj==unconfined op=collect_data cause=failed(directio) comm="syz-executor.4" name="file1" dev="sda1" ino=14305 res=0