[v6.1] kernel BUG in entry_points_to_object

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 4931e0e1673d Linux 6.1.170
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=164c576c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f0605c5af04d7603
dashboard link: https://syzkaller.appspot.com/bug?extid=f68d86b4a865ff83dcfc
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=103fd1ce580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1006f326580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/4c1b2399e351/disk-4931e0e1.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/feb034d7563a/vmlinux-4931e0e1.xz
kernel image: https://storage.googleapis.com/syzbot-assets/424a14bbc862/bzImage-4931e0e1.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/ccd137abf01a/mount_0.gz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=17dfd1ce580000)

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+f68d86...@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 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: 1 PID: 4432 Comm: syz.0.17 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026
RIP: 0010:__reiserfs_panic+0x167/0x170 fs/reiserfs/prints.c:390
Code: 80 55 9e 8a 48 0f 44 c8 4c 0f 44 f0 48 c7 c7 40 56 9e 8a 4c 89 fe 4c 89 f2 4c 8b 44 24 10 49 c7 c1 00 a0 d8 96 e8 29 81 ff ff <0f> 0b 0f 1f 80 00 00 00 00 53 48 89 fb e8 b7 48 5f f7 48 c7 c7 c0
RSP: 0018:ffffc90003447400 EFLAGS: 00010246
RAX: 0000000000000054 RBX: 1ffff92000688e84 RCX: 36191028120b2300
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffffc90003447510 R08: ffffc90003447107 R09: 1ffff92000688e20
R10: dffffc0000000000 R11: fffff52000688e21 R12: ffffc90003447440
R13: dffffc0000000000 R14: ffffffff8a9e0220 R15: ffff8880799bc6a8
FS: 0000555568c43500(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2e563fff CR3: 0000000075b22000 CR4: 00000000003506e0
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+0xf2c/0x1f00 fs/reiserfs/namei.c:1528
vfs_rename+0xbe1/0x1100 fs/namei.c:4882
do_renameat2+0x8e5/0xce0 fs/namei.c:5035
__do_sys_rename fs/namei.c:5081 [inline]
__se_sys_rename fs/namei.c:5079 [inline]
__x64_sys_rename+0x82/0x90 fs/namei.c:5079
do_syscall_x64 arch/x86/entry/common.c:46 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fdd7279cdd9
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 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 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffdbcfa6ac8 EFLAGS: 00000246 ORIG_RAX: 0000000000000052
RAX: ffffffffffffffda RBX: 00007fdd72a15fa0 RCX: 00007fdd7279cdd9
RDX: 0000000000000000 RSI: 00002000000002c0 RDI: 00002000000000c0
RBP: 00007fdd72832d69 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fdd72a15fac R14: 00007fdd72a15fa0 R15: 00007fdd72a15fa0
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:__reiserfs_panic+0x167/0x170 fs/reiserfs/prints.c:390
Code: 80 55 9e 8a 48 0f 44 c8 4c 0f 44 f0 48 c7 c7 40 56 9e 8a 4c 89 fe 4c 89 f2 4c 8b 44 24 10 49 c7 c1 00 a0 d8 96 e8 29 81 ff ff <0f> 0b 0f 1f 80 00 00 00 00 53 48 89 fb e8 b7 48 5f f7 48 c7 c7 c0
RSP: 0018:ffffc90003447400 EFLAGS: 00010246
RAX: 0000000000000054 RBX: 1ffff92000688e84 RCX: 36191028120b2300
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffffc90003447510 R08: ffffc90003447107 R09: 1ffff92000688e20
R10: dffffc0000000000 R11: fffff52000688e21 R12: ffffc90003447440
R13: dffffc0000000000 R14: ffffffff8a9e0220 R15: ffff8880799bc6a8
FS: 0000555568c43500(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2e563fff CR3: 0000000075b22000 CR4: 00000000003506e0
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