[v5.15] kernel BUG in entry_points_to_object

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: ac56c046adf4 Linux 5.15.195
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10e84704580000
kernel config: https://syzkaller.appspot.com/x/.config?x=e1bb6d24ef2164eb
dashboard link: https://syzkaller.appspot.com/bug?extid=3e1c055b88ff7d1b31ee
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15f1dd42580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12ad3614580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c11ec9487150/disk-ac56c046.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f1130a72d3a0/vmlinux-ac56c046.xz
kernel image: https://storage.googleapis.com/syzbot-assets/7608cb6a3be5/bzImage-ac56c046.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/b40fd34c28b6/mount_0.gz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=122e6932580000)

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

REISERFS warning (device loop0): vs-13060 reiserfs_update_sd_size: stat data of object [1 2 0x0 SD] (nlink == 1) not found (pos 2)
REISERFS (device loop0): Created .reiserfs_priv - reserved for xattr storage.
REISERFS warning (device loop0): vs-13060 reiserfs_update_sd_size: stat data of object [1 2 0x0 SD] (nlink == 1) not found (pos 2)
REISERFS warning (device loop0): vs-13060 reiserfs_update_sd_size: stat data of object [1 2 0x0 SD] (nlink == 1) not found (pos 2)
REISERFS panic (device loop0): vs-7042 entry_points_to_object: entry must be visible
------------[ cut here ]------------
kernel BUG at fs/reiserfs/prints.c:390!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 4314 Comm: syz.0.17 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
RIP: 0010:__reiserfs_panic+0x13a/0x140 fs/reiserfs/prints.c:390
Code: c7 c1 80 35 1b 8a 48 0f 44 c8 4c 0f 44 f0 48 c7 c7 40 36 1b 8a 4c 89 fe 4c 89 f2 49 89 d8 49 c7 c1 20 8e 1e 96 e8 96 51 ff ff <0f> 0b 0f 1f 40 00 53 48 89 fb e8 17 4d d8 f7 48 c7 c7 00 3f 1b 8a
RSP: 0018:ffffc900033ef440 EFLAGS: 00010246
RAX: 0000000000000054 RBX: ffffffff8bad261e RCX: 82291caec0488300
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffffc900033ef530 R08: dffffc0000000000 R09: ffffed10172067b0
R10: ffffed10172067b0 R11: 1ffff110172067af R12: ffffffff8a1ae420
R13: ffffc900033ef460 R14: ffffffff8a1ae400 R15: ffff888073e046a8
FS: 000055558d8d1500(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b31063fff CR3: 0000000023795000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
entry_points_to_object+0x7be/0x7d0 fs/reiserfs/namei.c:-1
reiserfs_rename+0xdf6/0x1eb0 fs/reiserfs/namei.c:1528
vfs_rename+0xbbf/0x10d0 fs/namei.c:4840
do_renameat2+0xa83/0xf70 fs/namei.c:4993
__do_sys_rename fs/namei.c:5039 [inline]
__se_sys_rename fs/namei.c:5037 [inline]
__x64_sys_rename+0x82/0x90 fs/namei.c:5037
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f78e6061fc9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffdcba19dd8 EFLAGS: 00000246 ORIG_RAX: 0000000000000052
RAX: ffffffffffffffda RBX: 00007f78e62b8fa0 RCX: 00007f78e6061fc9
RDX: 0000000000000000 RSI: 00002000000002c0 RDI: 00002000000000c0
RBP: 00007f78e60e4f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f78e62b8fa0 R14: 00007f78e62b8fa0 R15: 0000000000000002
</TASK>
Modules linked in:
---[ end trace df5b2885d267f7c8 ]---
RIP: 0010:__reiserfs_panic+0x13a/0x140 fs/reiserfs/prints.c:390
Code: c7 c1 80 35 1b 8a 48 0f 44 c8 4c 0f 44 f0 48 c7 c7 40 36 1b 8a 4c 89 fe 4c 89 f2 49 89 d8 49 c7 c1 20 8e 1e 96 e8 96 51 ff ff <0f> 0b 0f 1f 40 00 53 48 89 fb e8 17 4d d8 f7 48 c7 c7 00 3f 1b 8a
RSP: 0018:ffffc900033ef440 EFLAGS: 00010246
RAX: 0000000000000054 RBX: ffffffff8bad261e RCX: 82291caec0488300
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffffc900033ef530 R08: dffffc0000000000 R09: ffffed10172067b0
R10: ffffed10172067b0 R11: 1ffff110172067af R12: ffffffff8a1ae420
R13: ffffc900033ef460 R14: ffffffff8a1ae400 R15: ffff888073e046a8
FS: 000055558d8d1500(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b31063fff CR3: 0000000023795000 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 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