Hello, syzbot found the following issue on: HEAD commit: f66d6acccbc0 Merge tag 'x86_urgent_for_v6.12' of git://git.. git tree: upstream console+strace: https://syzkaller.appspot.com/x/log.txt?x=1381b2e8580000 kernel config: https://syzkaller.appspot.com/x/.config?x=570f86970553dcd2 dashboard link: https://syzkaller.appspot.com/bug?extid=2db3c7526ba68f4ea776 compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1400bb5f980000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=162c8ac0580000 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/83bb4f67b45d/disk-f66d6acc.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/cb0cedffb310/vmlinux-f66d6acc.xz kernel image: https://storage.googleapis.com/syzbot-assets/3af8c8949657/bzImage-f66d6acc.xz mounted in repro: https://storage.googleapis.com/syzbot-assets/bfaab1c46dcf/mount_0.gz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+2db3c7526ba68f4ea776@xxxxxxxxxxxxxxxxxxxxxxxxx loop0: detected capacity change from 0 to 64 ===================================================== BUG: KMSAN: uninit-value in hfs_inode_read_fork fs/hfs/inode.c:287 [inline] BUG: KMSAN: uninit-value in hfs_read_inode+0x10ae/0x1690 fs/hfs/inode.c:343 hfs_inode_read_fork fs/hfs/inode.c:287 [inline] hfs_read_inode+0x10ae/0x1690 fs/hfs/inode.c:343 inode_insert5+0x1dd/0x970 fs/inode.c:1281 iget5_locked+0xfe/0x1d0 fs/inode.c:1338 hfs_iget+0x121/0x240 fs/hfs/inode.c:403 hfs_fill_super+0x2098/0x23c0 fs/hfs/super.c:431 mount_bdev+0x39a/0x520 fs/super.c:1693 hfs_mount+0x4d/0x60 fs/hfs/super.c:457 legacy_get_tree+0x114/0x290 fs/fs_context.c:662 vfs_get_tree+0xb1/0x5a0 fs/super.c:1814 do_new_mount+0x71f/0x15e0 fs/namespace.c:3507 path_mount+0x742/0x1f10 fs/namespace.c:3834 do_mount fs/namespace.c:3847 [inline] __do_sys_mount fs/namespace.c:4057 [inline] __se_sys_mount+0x722/0x810 fs/namespace.c:4034 __x64_sys_mount+0xe4/0x150 fs/namespace.c:4034 x64_sys_call+0x255a/0x3ba0 arch/x86/include/generated/asm/syscalls_64.h:166 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f Local variable rec created at: hfs_fill_super+0x67/0x23c0 fs/hfs/super.c:383 mount_bdev+0x39a/0x520 fs/super.c:1693 CPU: 1 UID: 0 PID: 5790 Comm: syz-executor415 Not tainted 6.12.0-rc7-syzkaller-00216-gf66d6acccbc0 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/30/2024 ===================================================== --- This report is generated by a bot. It may contain errors. See https://goo.gl/tpsmEJ for more information about syzbot. syzbot engineers can be reached at syzkaller@xxxxxxxxxxxxxxxx. syzbot will keep track of this issue. See: https://goo.gl/tpsmEJ#status for how to communicate with syzbot. If the report is already addressed, let syzbot know by replying with: #syz fix: exact-commit-title If you want syzbot to run the reproducer, reply with: #syz test: git://repo/address.git branch-or-commit-hash If you attach or paste a git patch, syzbot will apply it before testing. If you want to overwrite report's subsystems, reply with: #syz set subsystems: new-subsystem (See the list of subsystem names on the web dashboard) If the report is a duplicate of another one, reply with: #syz dup: exact-subject-of-another-report If you want to undo deduplication, reply with: #syz undup
