[v6.1] kernel BUG in direntry_check_right

3 views
Skip to first unread message

syzbot

unread,
Mar 26, 2025, 11:43:37 AM3/26/25
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 344a09659766 Linux 6.1.131
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=165baa4c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=14d5dbae75afa499
dashboard link: https://syzkaller.appspot.com/bug?extid=c8047ec9b25cceccad70
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8c94453bbad3/disk-344a0965.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/6bf26518c790/vmlinux-344a0965.xz
kernel image: https://storage.googleapis.com/syzbot-assets/424da9a470eb/Image-344a0965.gz.xz

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

------------[ cut here ]------------
kernel BUG at fs/reiserfs/item_ops.c:569!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 8076 Comm: syz.0.917 Not tainted 6.1.131-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : direntry_check_right+0x224/0x230 fs/reiserfs/item_ops.c:561
lr : direntry_check_right+0x224/0x230 fs/reiserfs/item_ops.c:561
sp : ffff800021386950
x29: ffff800021386950 x28: dfff800000000000 x27: 1ffff00004270dfe
x26: 0000000000000018 x25: 0000000000000002 x24: 00000000fffffffe
x23: dfff800000000000 x22: 0000000000000090 x21: 0000000000000014
x20: 0000000000000003 x19: ffff0000d4e60198 x18: ffff800021386bde
x17: ffff800008a7bfe0 x16: ffff800012275c40 x15: 0000000000000002
x14: 0000000000000070 x13: ffff0000d6925340 x12: 0000000000080000
x11: 00000000000051c5 x10: ffff8000222fb000 x9 : ffff800008dcec58
x8 : 00000000000051c6 x7 : 0000000000000000 x6 : 000000000000003f
x5 : 0000000000000040 x4 : ffffffffffffffd0 x3 : 00000000ffffffe8
x2 : 00000000000002dc x1 : 0000000000000090 x0 : 00000000000000a4
Call trace:
direntry_check_right+0x224/0x230 fs/reiserfs/item_ops.c:561
check_right+0x400/0x644 fs/reiserfs/fix_node.c:355
dc_check_balance_leaf fs/reiserfs/fix_node.c:1983 [inline]
dc_check_balance fs/reiserfs/fix_node.c:2039 [inline]
check_balance fs/reiserfs/fix_node.c:2086 [inline]
fix_nodes+0x27e4/0x7078 fs/reiserfs/fix_node.c:2635
reiserfs_cut_from_item+0x330/0x1c98 fs/reiserfs/stree.c:1742
reiserfs_rename+0x1780/0x1c88 fs/reiserfs/namei.c:1628
vfs_rename+0xac8/0xe04 fs/namei.c:4874
do_renameat2+0x9ec/0xe64 fs/namei.c:5027
__do_sys_renameat2 fs/namei.c:5060 [inline]
__se_sys_renameat2 fs/namei.c:5057 [inline]
__arm64_sys_renameat2+0xe0/0xfc fs/namei.c:5057
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585
Code: 52800041 97eea41f 17ffff9a 97dc97ea (d4210000)
---[ end trace 0000000000000000 ]---


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

unread,
Mar 26, 2025, 10:08:31 PM3/26/25
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:

HEAD commit: 344a09659766 Linux 6.1.131
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1497d43f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=14d5dbae75afa499
dashboard link: https://syzkaller.appspot.com/bug?extid=c8047ec9b25cceccad70
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14e66198580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11916de4580000
mounted in repro: https://storage.googleapis.com/syzbot-assets/5ff4ffeb2d44/mount_0.gz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=15bf8a4c580000)

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

REISERFS warning (device loop0): vs-13060 reiserfs_update_sd_size: stat data of object [1 2 0x0 SD] (nlink == 6) not found (pos 2)
REISERFS warning (device loop0): vs-13060 reiserfs_update_sd_size: stat data of object [1 2 0x0 SD] (nlink == 6) not found (pos 2)
------------[ cut here ]------------
kernel BUG at fs/reiserfs/item_ops.c:569!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 4292 Comm: syz-executor232 Not tainted 6.1.131-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : direntry_check_right+0x224/0x230 fs/reiserfs/item_ops.c:561
lr : direntry_check_right+0x224/0x230 fs/reiserfs/item_ops.c:561
sp : ffff8000215c6950
x29: ffff8000215c6950 x28: dfff800000000000 x27: 1ffff000042b8dfe
x26: 0000000000000018 x25: 0000000000000002 x24: 00000000fffffffe
x23: dfff800000000000 x22: 0000000000000090 x21: 0000000000000014
x20: 0000000000000003 x19: ffff0000d9008198 x18: ffff8000215c6bde
x17: ffff800008a7bfe0 x16: ffff800012275c40 x15: 0000000000000000
x14: 0000000000000070 x13: ffff0000d0e98000 x12: 0000000000ff0100
x11: 0000000000ff0100 x10: 0000000000000000 x9 : ffff800008dcec58
x8 : ffff0000d0e98000 x7 : 0000000000000000 x6 : 000000000000003f
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.
Reply all
Reply to author
Forward
0 new messages