kernel BUG at fs/reiserfs/prints.c:LINE!

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: cbfa1702 Linux 4.14.198
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16ed163d900000
kernel config: https://syzkaller.appspot.com/x/.config?x=3990958d85b55e59
dashboard link: https://syzkaller.appspot.com/bug?extid=511567b57e0eb92bdf00
compiler: gcc (GCC) 10.1.0-syz 20200507
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=114f85c5900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=159de087900000

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

REISERFS (device loop0): using 3.5.x disk format
REISERFS (device loop0): Created .reiserfs_priv - reserved for xattr storage.
REISERFS panic (device loop0): journal-2332 do_journal_end: Trying to log block 8211, which is a log block
------------[ cut here ]------------
kernel BUG at fs/reiserfs/prints.c:390!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
Modules linked in:
CPU: 0 PID: 6350 Comm: syz-executor796 Not tainted 4.14.198-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
task: ffff8880986e20c0 task.stack: ffff888097e78000
RIP: 0010:__reiserfs_panic.cold+0x37/0x8a fs/reiserfs/prints.c:390
RSP: 0018:ffff888097e7f9f8 EFLAGS: 00010297
RAX: ffff8880986e20c0 RBX: ffff88809808a780 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff86ac12c0 RDI: ffffed1012fcff35
RBP: ffff888097e7faa8 R08: 000000000000006a R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: ffffffff86b76b40
R13: ffffffff86b77340 R14: ffffffff86b710c0 R15: ffffc90005a7a0d8
FS: 0000000000990880(0000) GS:ffff8880aea00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000006d00a0 CR3: 0000000007c6a000 CR4: 00000000001406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
do_journal_end+0x3777/0x41d0 fs/reiserfs/journal.c:4146
reiserfs_sync_fs+0xbb/0xd0 fs/reiserfs/super.c:78
__sync_filesystem fs/sync.c:39 [inline]
sync_filesystem fs/sync.c:64 [inline]
sync_filesystem+0xe2/0x230 fs/sync.c:48
generic_shutdown_super+0x70/0x370 fs/super.c:432
kill_block_super+0x95/0xe0 fs/super.c:1161
deactivate_locked_super+0x6c/0xd0 fs/super.c:319
deactivate_super+0x7f/0xa0 fs/super.c:350
cleanup_mnt+0x186/0x2c0 fs/namespace.c:1183
task_work_run+0x11f/0x190 kernel/task_work.c:113
exit_task_work include/linux/task_work.h:22 [inline]
do_exit+0xa08/0x27f0 kernel/exit.c:865
do_group_exit+0x100/0x2e0 kernel/exit.c:962
SYSC_exit_group kernel/exit.c:973 [inline]
SyS_exit_group+0x19/0x20 kernel/exit.c:971
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x4437a8
RSP: 002b:00007ffcdbc34918 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00000000004437a8
RDX: 0000000000000001 RSI: 000000000000003c RDI: 0000000000000001
RBP: 00000000004c3c50 R08: 00000000000000e7 R09: ffffffffffffffd0
R10: 0000000000000800 R11: 0000000000000246 R12: 0000000000000001
R13: 00000000006d6180 R14: 0000000000000000 R15: 0000000000000000
Code: 10 b7 86 74 6d e8 7c d8 a4 ff 4c 89 e9 4c 89 f2 4c 89 e6 49 c7 c0 e0 83 61 8a 48 c7 c7 80 12 b7 86 e8 c1 77 93 ff e8 5b d8 a4 ff <0f> 0b e8 54 d8 a4 ff 4d 85 e4 49 c7 c6 c0 10 b7 86 75 0a 49 c7
RIP: __reiserfs_panic.cold+0x37/0x8a fs/reiserfs/prints.c:390 RSP: ffff888097e7f9f8
---[ end trace dae301052e37ad6b ]---


---
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.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches

[syzbot]

syzbot suspects this issue was fixed by commit:

commit b74d5f70523a819aac71e0eee4f4b530e69e463a
Author: Rustam Kovhaev <rkov...@gmail.com>
Date: Sun Nov 1 14:09:58 2020 +0000

reiserfs: add check for an invalid ih_entry_count

bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13114ffb500000
start commit: 2b791501 Linux 4.14.203
git tree: linux-4.14.y
kernel config: https://syzkaller.appspot.com/x/.config?x=e52bb6f2a595a463
dashboard link: https://syzkaller.appspot.com/bug?extid=511567b57e0eb92bdf00
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=103565f4500000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=131e2532500000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: reiserfs: add check for an invalid ih_entry_count

For information about bisection process see: https://goo.gl/tpsmEJ#bisection