audit: type=1804 audit(1671563255.519:102): pid=15858 uid=0 auid=4294967295 ses=4294967295 subj==unconfined op=invalid_pcr cause=open_writers comm="syz-executor.1" name="/root/syzkaller-testdir2669126518/syzkaller.x7GShm/155/file0/file0" dev="loop1" ino=49 res=1 ====================================================== WARNING: possible circular locking dependency detected 4.19.211-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.4/15843 is trying to acquire lock: 0000000049456f2b (&sbi->alloc_mutex){+.+.}, at: hfsplus_block_free+0xdb/0x5d0 fs/hfsplus/bitmap.c:182 but task is already holding lock: 0000000009181bb7 (&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] hfsplus_block_allocate+0x197/0xa60 fs/hfsplus/bitmap.c:37 hfsplus_file_extend+0x436/0xf40 fs/hfsplus/extents.c:468 hfsplus_get_block+0x196/0x960 fs/hfsplus/extents.c:245 __block_write_begin_int+0x46c/0x17b0 fs/buffer.c:1978 __block_write_begin fs/buffer.c:2028 [inline] block_write_begin+0x58/0x2e0 fs/buffer.c:2087 cont_write_begin+0x55a/0x820 fs/buffer.c:2440 hfsplus_write_begin+0x87/0x150 fs/hfsplus/inode.c:52 generic_perform_write+0x1f8/0x4d0 mm/filemap.c:3170 __generic_file_write_iter+0x24b/0x610 mm/filemap.c:3295 generic_file_write_iter+0x3f8/0x730 mm/filemap.c:3323 call_write_iter include/linux/fs.h:1821 [inline] aio_write+0x37f/0x5c0 fs/aio.c:1574 __io_submit_one fs/aio.c:1858 [inline] io_submit_one+0xecd/0x20c0 fs/aio.c:1909 __do_sys_io_submit fs/aio.c:1953 [inline] __se_sys_io_submit+0x11b/0x4a0 fs/aio.c:1924 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe -> #0 (&sbi->alloc_mutex){+.+.}: __mutex_lock_common kernel/locking/mutex.c:937 [inline] __mutex_lock+0xd7/0x1190 kernel/locking/mutex.c:1078 hfsplus_block_free+0xdb/0x5d0 fs/hfsplus/bitmap.c:182 hfsplus_free_extents+0x228/0x520 fs/hfsplus/extents.c:363 hfsplus_file_truncate+0xd96/0x1040 fs/hfsplus/extents.c:591 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(&sbi->alloc_mutex); lock(&HFSPLUS_I(inode)->extents_lock); lock(&sbi->alloc_mutex); *** DEADLOCK *** 8 locks held by syz-executor.4/15843: #0: 000000007fd20a5f (sb_writers#15){.+.+}, at: sb_start_write include/linux/fs.h:1579 [inline] #0: 000000007fd20a5f (sb_writers#15){.+.+}, at: mnt_want_write+0x3a/0xb0 fs/namespace.c:360 #1: 0000000083030ae0 (&type->s_vfs_rename_key#3){+.+.}, at: lock_rename+0x54/0x280 fs/namei.c:2867 #2: 00000000f70d9548 (&type->i_mutex_dir_key#9/1){+.+.}, at: inode_lock_nested include/linux/fs.h:783 [inline] #2: 00000000f70d9548 (&type->i_mutex_dir_key#9/1){+.+.}, at: lock_rename+0x132/0x280 fs/namei.c:2878 #3: 0000000078fc42b8 (&type->i_mutex_dir_key#9/2){+.+.}, at: inode_lock_nested include/linux/fs.h:783 [inline] #3: 0000000078fc42b8 (&type->i_mutex_dir_key#9/2){+.+.}, at: lock_rename+0x166/0x280 fs/namei.c:2879 #4: 0000000082942eab (&sb->s_type->i_mutex_key#22){+.+.}, at: inode_lock include/linux/fs.h:748 [inline] #4: 0000000082942eab (&sb->s_type->i_mutex_key#22){+.+.}, at: lock_two_nondirectories+0xec/0x110 fs/inode.c:1015 #5: 0000000077008755 (&sb->s_type->i_mutex_key#22/4){+.+.}, at: inode_lock_nested include/linux/fs.h:783 [inline] #5: 0000000077008755 (&sb->s_type->i_mutex_key#22/4){+.+.}, at: lock_two_nondirectories+0xd1/0x110 fs/inode.c:1017 #6: 00000000f3188875 (&sbi->vh_mutex){+.+.}, at: hfsplus_unlink+0x140/0x820 fs/hfsplus/dir.c:370 #7: 0000000009181bb7 (&HFSPLUS_I(inode)->extents_lock){+.+.}, at: hfsplus_file_truncate+0x1e2/0x1040 fs/hfsplus/extents.c:576 stack backtrace: CPU: 0 PID: 15843 Comm: syz-executor.4 Not tainted 4.19.211-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022 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_block_free+0xdb/0x5d0 fs/hfsplus/bitmap.c:182 hfsplus_free_extents+0x228/0x520 fs/hfsplus/extents.c:363 hfsplus_file_truncate+0xd96/0x1040 fs/hfsplus/extents.c:591 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:0x7fb3ebb1a0d9 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:00007fb3ea08c168 EFLAGS: 00000246 ORIG_RAX: 0000000000000052 RAX: ffffffffffffffda RBX: 00007fb3ebc39f80 RCX: 00007fb3ebb1a0d9 RDX: 0000000000000000 RSI: 0000000020000140 RDI: 0000000020000000 RBP: 00007fb3ebb75ae9 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffc97c4c1df R14: 00007fb3ea08c300 R15: 0000000000022000 FAT-fs (loop1): Unrecognized mount option "ÿÿÿÿp" or missing value attempt to access beyond end of device loop4: rw=0, want=201326594, limit=1024 Buffer I/O error on dev loop4, logical block 100663296, async page read hfsplus: unable to mark blocks free: error -5 hfsplus: can't free extent kauditd_printk_skb: 1 callbacks suppressed audit: type=1800 audit(1671563256.669:104): pid=15870 uid=0 auid=4294967295 ses=4294967295 subj==unconfined op=collect_data cause=failed(directio) comm="syz-executor.3" name="file0" dev="loop3" ino=50 res=0 audit: type=1804 audit(1671563256.719:105): pid=15870 uid=0 auid=4294967295 ses=4294967295 subj==unconfined op=invalid_pcr cause=open_writers comm="syz-executor.3" name="/root/syzkaller-testdir3960937289/syzkaller.q22N0z/173/file0/file0" dev="loop3" ino=50 res=1 attempt to access beyond end of device audit: type=1800 audit(1671563257.060:106): pid=15904 uid=0 auid=4294967295 ses=4294967295 subj==unconfined op=collect_data cause=failed(directio) comm="syz-executor.1" name="file0" dev="loop1" ino=51 res=0 loop4: rw=0, want=201326594, limit=1024 attempt to access beyond end of device audit: type=1804 audit(1671563257.100:107): pid=15904 uid=0 auid=4294967295 ses=4294967295 subj==unconfined op=invalid_pcr cause=open_writers comm="syz-executor.1" name="/root/syzkaller-testdir2669126518/syzkaller.x7GShm/157/file0/file0" dev="loop1" ino=51 res=1 loop2: rw=0, want=201326594, limit=1024 Buffer I/O error on dev loop4, logical block 100663296, async page read Buffer I/O error on dev loop2, logical block 100663296, async page read hfsplus: unable to mark blocks free: error -5 IPv6: ADDRCONF(NETDEV_CHANGE): vcan0: link becomes ready hfsplus: unable to mark blocks free: error -5 hfsplus: can't free extent hfsplus: can't free extent IPv6: ADDRCONF(NETDEV_CHANGE): vxcan0: link becomes ready IPv6: ADDRCONF(NETDEV_CHANGE): vxcan1: link becomes ready attempt to access beyond end of device loop2: rw=0, want=201326594, limit=1024 JFS: discard option not supported on device attempt to access beyond end of device Buffer I/O error on dev loop2, logical block 100663296, async page read loop4: rw=0, want=201326594, limit=1024 hfsplus: unable to mark blocks free: error -5 Buffer I/O error on dev loop4, logical block 100663296, async page read hfsplus: can't free extent hfsplus: unable to mark blocks free: error -5 IPv6: ADDRCONF(NETDEV_CHANGE): vcan0: link becomes ready hfsplus: can't free extent IPv6: ADDRCONF(NETDEV_CHANGE): vxcan0: link becomes ready IPv6: ADDRCONF(NETDEV_CHANGE): vxcan1: link becomes ready attempt to access beyond end of device loop4: rw=0, want=201326594, limit=1024 Buffer I/O error on dev loop4, logical block 100663296, async page read hfsplus: unable to mark blocks free: error -5 hfsplus: can't free extent attempt to access beyond end of device loop2: rw=0, want=201326594, limit=1024 Buffer I/O error on dev loop2, logical block 100663296, async page read hfsplus: unable to mark blocks free: error -5 hfsplus: can't free extent A link change request failed with some changes committed already. Interface team_slave_0 may have been left with an inconsistent configuration, please check. syz-executor.0 (15971) used greatest stack depth: 23056 bytes left JFS: discard option not supported on device IPv6: ADDRCONF(NETDEV_CHANGE): vcan0: link becomes ready IPv6: ADDRCONF(NETDEV_CHANGE): vxcan0: link becomes ready IPv6: ADDRCONF(NETDEV_CHANGE): vxcan1: link becomes ready JFS: discard option not supported on device A link change request failed with some changes committed already. Interface veth0_to_bond may have been left with an inconsistent configuration, please check. IPv6: ADDRCONF(NETDEV_CHANGE): vcan0: link becomes ready IPv6: ADDRCONF(NETDEV_CHANGE): vxcan0: link becomes ready IPv6: ADDRCONF(NETDEV_CHANGE): vxcan1: link becomes ready JFS: discard option not supported on device A link change request failed with some changes committed already. Interface team_slave_1 may have been left with an inconsistent configuration, please check. JFS: discard option not supported on device JFS: discard option not supported on device JFS: discard option not supported on device IPVS: ftp: loaded support on port[0] = 21 IPVS: ftp: loaded support on port[0] = 21