Hello,
syzbot found the following issue on:
HEAD commit: 60a9e718726f Linux 6.6.106
git tree: linux-6.6.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=160ffb12580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=12606d4b8832c7e4
dashboard link:
https://syzkaller.appspot.com/bug?extid=374747cc9408d4e3981b
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/eca27e056a5a/disk-60a9e718.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/bc64d4eeb7f6/vmlinux-60a9e718.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/a345041561ac/bzImage-60a9e718.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+374747...@syzkaller.appspotmail.com
REISERFS panic (device loop2): journal-2332 do_journal_end: Trying to log block 531, which is a log block
------------[ cut here ]------------
kernel BUG at fs/reiserfs/prints.c:390!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 6295 Comm: syz.1.95 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025
RIP: 0010:__reiserfs_panic+0x13e/0x140 fs/reiserfs/prints.c:390
Code: c7 c1 40 90 bc 8a 48 0f 44 c8 4c 0f 44 f0 48 c7 c7 00 91 bc 8a 4c 89 fe 4c 89 f2 49 89 d8 49 c7 c1 c0 90 fd 96 e8 12 66 ff ff <0f> 0b 66 0f 1f 00 53 48 89 fb e8 03 2b 22 f7 48 c7 c7 80 99 bc 8a
RSP: 0018:ffffc9000c4ef9e0 EFLAGS: 00010246
RAX: 0000000000000069 RBX: ffffffff8c7b8419 RCX: 2c725d2b42a92600
RDX: ffffc9000d825000 RSI: 000000000001364a RDI: 000000000001364b
RBP: ffffc9000c4efad0 R08: ffffc9000c4ef6e7 R09: 1ffff9200189dedc
R10: dffffc0000000000 R11: fffff5200189dedd R12: ffffffff8abcdd40
R13: ffffc9000c4efa00 R14: ffffffff8abcdd20 R15: ffff88805bc4c660
FS: 00007f104bac06c0(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2e22421c CR3: 0000000030c26000 CR4: 00000000003506e0
Call Trace:
<TASK>
do_journal_end+0x3f66/0x4860 fs/reiserfs/journal.c:4156
reiserfs_sync_fs+0xd0/0x150 fs/reiserfs/super.c:78
iterate_supers+0xb2/0x170 fs/super.c:979
ksys_sync+0xa4/0x150 fs/sync.c:103
__ia32_sys_sync+0xe/0x20 fs/sync.c:113
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f104ab8eba9
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:00007f104bac0038 EFLAGS: 00000246 ORIG_RAX: 00000000000000a2
RAX: ffffffffffffffda RBX: 00007f104add5fa0 RCX: 00007f104ab8eba9
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 00007f104add5fa0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f104add6038 R14: 00007f104add5fa0 R15: 00007fffc987e3e8
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:__reiserfs_panic+0x13e/0x140 fs/reiserfs/prints.c:390
Code: c7 c1 40 90 bc 8a 48 0f 44 c8 4c 0f 44 f0 48 c7 c7 00 91 bc 8a 4c 89 fe 4c 89 f2 49 89 d8 49 c7 c1 c0 90 fd 96 e8 12 66 ff ff <0f> 0b 66 0f 1f 00 53 48 89 fb e8 03 2b 22 f7 48 c7 c7 80 99 bc 8a
RSP: 0018:ffffc9000c4ef9e0 EFLAGS: 00010246
RAX: 0000000000000069 RBX: ffffffff8c7b8419 RCX: 2c725d2b42a92600
RDX: ffffc9000d825000 RSI: 000000000001364a RDI: 000000000001364b
RBP: ffffc9000c4efad0 R08: ffffc9000c4ef6e7 R09: 1ffff9200189dedc
R10: dffffc0000000000 R11: fffff5200189dedd R12: ffffffff8abcdd40
R13: ffffc9000c4efa00 R14: ffffffff8abcdd20 R15: ffff88805bc4c660
FS: 00007f104bac06c0(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fceef3c9f98 CR3: 0000000030c26000 CR4: 00000000003506f0
---
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