[v6.1] kernel BUG in hfs_btree_open (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 3a8358583626 Linux 6.1.129
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1572e7a4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=d841937c118666c6
dashboard link: https://syzkaller.appspot.com/bug?extid=c477e4e8d821b324a209
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/13f8e53cc467/disk-3a835858.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/a85676a44932/vmlinux-3a835858.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9e9dcc0eaae9/bzImage-3a835858.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+c477e4...@syzkaller.appspotmail.com

loop4: detected capacity change from 0 to 64
------------[ cut here ]------------
kernel BUG at fs/hfs/btree.c:41!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 17616 Comm: syz.4.3696 Not tainted 6.1.129-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 12/27/2024
RIP: 0010:hfs_btree_open+0xf05/0xf20 fs/hfs/btree.c:41
Code: 80 ff e9 7e fa ff ff 44 89 f1 80 e1 07 80 c1 03 38 c1 0f 8c 9b fa ff ff 4c 89 f7 e8 c5 08 80 ff e9 8e fa ff ff e8 1b b0 28 ff <0f> 0b e8 14 b0 28 ff 0f 0b e8 0d b0 28 ff 0f 0b 66 2e 0f 1f 84 00
RSP: 0018:ffffc90006a3f798 EFLAGS: 00010287
RAX: ffffffff8261e6b5 RBX: ffff888054ebe1a0 RCX: 0000000000080000
RDX: ffffc90010648000 RSI: 0000000000001a2c RDI: 0000000000001a2d
RBP: 0000000000000000 R08: ffffffff8261d913 R09: ffffed100a9d7c50
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff8880784b8000
R13: ffff888065e38008 R14: ffff888065e38000 R15: dffffc0000000000
FS: 00007ff6c95366c0(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ff6c87705a0 CR3: 000000007b4ee000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
hfs_mdb_get+0x1442/0x21b0 fs/hfs/mdb.c:199
hfs_fill_super+0x1065/0x17f0 fs/hfs/super.c:406
mount_bdev+0x2c9/0x3f0 fs/super.c:1443
legacy_get_tree+0xeb/0x180 fs/fs_context.c:632
vfs_get_tree+0x88/0x270 fs/super.c:1573
do_new_mount+0x2ba/0xb40 fs/namespace.c:3056
do_mount fs/namespace.c:3399 [inline]
__do_sys_mount fs/namespace.c:3607 [inline]
__se_sys_mount+0x2d5/0x3c0 fs/namespace.c:3584
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7ff6c878e90a
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 de 1a 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ff6c9535e68 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007ff6c9535ef0 RCX: 00007ff6c878e90a
RDX: 0000400000000180 RSI: 0000400000000080 RDI: 00007ff6c9535eb0
RBP: 0000400000000180 R08: 00007ff6c9535ef0 R09: 0000000002000000
R10: 0000000002000000 R11: 0000000000000246 R12: 0000400000000080
R13: 00007ff6c9535eb0 R14: 00000000000002eb R15: 00004000000006c0
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:hfs_btree_open+0xf05/0xf20 fs/hfs/btree.c:41
Code: 80 ff e9 7e fa ff ff 44 89 f1 80 e1 07 80 c1 03 38 c1 0f 8c 9b fa ff ff 4c 89 f7 e8 c5 08 80 ff e9 8e fa ff ff e8 1b b0 28 ff <0f> 0b e8 14 b0 28 ff 0f 0b e8 0d b0 28 ff 0f 0b 66 2e 0f 1f 84 00
RSP: 0018:ffffc90006a3f798 EFLAGS: 00010287
RAX: ffffffff8261e6b5 RBX: ffff888054ebe1a0 RCX: 0000000000080000
RDX: ffffc90010648000 RSI: 0000000000001a2c RDI: 0000000000001a2d
RBP: 0000000000000000 R08: ffffffff8261d913 R09: ffffed100a9d7c50
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff8880784b8000
R13: ffff888065e38008 R14: ffff888065e38000 R15: dffffc0000000000
FS: 00007ff6c95366c0(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055e93d4c2000 CR3: 000000007b4ee000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


---
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 syzk...@googlegroups.com.

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 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

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.