loop4: detected capacity change from 0 to 1024 ===================================================== BUG: KMSAN: uninit-value in hfsplus_subfolders_dec fs/hfsplus/catalog.c:248 [inline] BUG: KMSAN: uninit-value in hfsplus_delete_cat+0x10f0/0x1350 fs/hfsplus/catalog.c:419 hfsplus_subfolders_dec fs/hfsplus/catalog.c:248 [inline] hfsplus_delete_cat+0x10f0/0x1350 fs/hfsplus/catalog.c:419 hfsplus_rmdir+0x140/0x2e0 fs/hfsplus/dir.c:425 vfs_rmdir+0x5b1/0x790 fs/namei.c:4206 do_rmdir+0x630/0x8b0 fs/namei.c:4265 __do_sys_rmdir fs/namei.c:4284 [inline] __se_sys_rmdir fs/namei.c:4282 [inline] __x64_sys_rmdir+0x78/0xb0 fs/namei.c:4282 x64_sys_call+0x3a8e/0x3b50 arch/x86/include/generated/asm/syscalls_64.h:85 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcf/0x1e0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f Uninit was stored to memory at: hfsplus_subfolders_inc fs/hfsplus/catalog.c:232 [inline] hfsplus_create_cat+0x1804/0x1810 fs/hfsplus/catalog.c:314 hfsplus_mknod+0x201/0x570 fs/hfsplus/dir.c:494 hfsplus_mkdir+0x58/0x70 fs/hfsplus/dir.c:529 vfs_mkdir+0x49e/0x710 fs/namei.c:4123 do_mkdirat+0x529/0x810 fs/namei.c:4146 __do_sys_mkdir fs/namei.c:4166 [inline] __se_sys_mkdir fs/namei.c:4164 [inline] __x64_sys_mkdir+0xa1/0xf0 fs/namei.c:4164 x64_sys_call+0x12e0/0x3b50 arch/x86/include/generated/asm/syscalls_64.h:84 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcf/0x1e0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f Uninit was created at: __alloc_pages+0x9d6/0xe70 mm/page_alloc.c:4598 __alloc_pages_node include/linux/gfp.h:238 [inline] alloc_pages_node include/linux/gfp.h:261 [inline] alloc_slab_page mm/slub.c:2175 [inline] allocate_slab mm/slub.c:2338 [inline] new_slab+0x2de/0x1400 mm/slub.c:2391 ___slab_alloc+0x1184/0x33d0 mm/slub.c:3525 __slab_alloc mm/slub.c:3610 [inline] __slab_alloc_node mm/slub.c:3663 [inline] slab_alloc_node mm/slub.c:3835 [inline] kmem_cache_alloc_lru+0x6d7/0xbe0 mm/slub.c:3864 alloc_inode_sb include/linux/fs.h:3091 [inline] hfsplus_alloc_inode+0x5a/0xd0 fs/hfsplus/super.c:633 alloc_inode+0x86/0x460 fs/inode.c:261 iget_locked+0x2bf/0xee0 fs/inode.c:1280 hfsplus_iget+0x59/0xaf0 fs/hfsplus/super.c:64 hfsplus_btree_open+0x13e/0x1d10 fs/hfsplus/btree.c:150 hfsplus_fill_super+0x1113/0x2700 fs/hfsplus/super.c:479 mount_bdev+0x397/0x520 fs/super.c:1658 hfsplus_mount+0x4d/0x60 fs/hfsplus/super.c:647 legacy_get_tree+0x114/0x290 fs/fs_context.c:662 vfs_get_tree+0xa7/0x570 fs/super.c:1779 do_new_mount+0x71f/0x15e0 fs/namespace.c:3352 path_mount+0x742/0x1f20 fs/namespace.c:3679 do_mount fs/namespace.c:3692 [inline] __do_sys_mount fs/namespace.c:3898 [inline] __se_sys_mount+0x725/0x810 fs/namespace.c:3875 __x64_sys_mount+0xe4/0x150 fs/namespace.c:3875 x64_sys_call+0x2bf4/0x3b50 arch/x86/include/generated/asm/syscalls_64.h:166 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcf/0x1e0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f CPU: 0 PID: 9419 Comm: syz-executor.4 Not tainted 6.9.0-rc4-syzkaller-00038-g8cd26fd90c1a #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024 =====================================================