general protection fault in do_journal_end

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 3f8a27f9e27b Linux 4.19.211
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=171132a7880000
kernel config: https://syzkaller.appspot.com/x/.config?x=9b9277b418617afe
dashboard link: https://syzkaller.appspot.com/bug?extid=757cbeb62a22b9a7cc96
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13065829880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=119b87c3880000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/98c0bdb4abb3/disk-3f8a27f9.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ea228ff02669/vmlinux-3f8a27f9.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/3641d50a74e5/mount_0.gz

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

REISERFS (device loop0): Created .reiserfs_priv - reserved for xattr storage.
audit: type=1800 audit(1669781740.550:2): pid=8111 uid=0 auid=4294967295 ses=4294967295 subj==unconfined op=collect_data cause=failed(directio) comm="syz-executor261" name="bus" dev="loop0" ino=4 res=0
kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 8111 Comm: syz-executor261 Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
RIP: 0010:constant_test_bit arch/x86/include/asm/bitops.h:317 [inline]
RIP: 0010:set_buffer_uptodate include/linux/buffer_head.h:120 [inline]
RIP: 0010:do_journal_end+0x12cd/0x4840 fs/reiserfs/journal.c:4093
Code: 0f 85 cf 2b 00 00 48 8b 7b 18 b9 08 00 00 00 e8 79 c6 d9 ff 48 89 c2 48 89 44 24 78 48 b8 00 00 00 00 00 fc ff df 48 c1 ea 03 <80> 3c 02 00 0f 85 92 2b 00 00 4c 8b 74 24 78 31 ff 49 8b 1e 83 e3
RSP: 0018:ffff8880b1387a08 EFLAGS: 00010246
RAX: dffffc0000000000 RBX: ffffc90001b1a000 RCX: ffffffff81b0a8f6
RDX: 0000000000000000 RSI: ffffffff81b0ac88 RDI: 0000000000000005
RBP: ffff888089d25000 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: 0000000000000000
R13: 000000000000001e R14: ffff8880b1387b50 R15: ffffc90001b1a000
FS: 0000555555f01300(0000) GS:ffff8880ba100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055eaa3b310e8 CR3: 00000000997c3000 CR4: 00000000003406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
reiserfs_sync_fs+0xf8/0x120 fs/reiserfs/super.c:78
__sync_filesystem fs/sync.c:39 [inline]
sync_filesystem+0x105/0x250 fs/sync.c:64
generic_shutdown_super+0x70/0x370 fs/super.c:442
kill_block_super+0x97/0xf0 fs/super.c:1185
deactivate_locked_super+0x94/0x160 fs/super.c:329
deactivate_super+0x174/0x1a0 fs/super.c:360
cleanup_mnt+0x1a8/0x290 fs/namespace.c:1098
task_work_run+0x148/0x1c0 kernel/task_work.c:113
exit_task_work include/linux/task_work.h:22 [inline]
do_exit+0xbf3/0x2be0 kernel/exit.c:870
do_group_exit+0x125/0x310 kernel/exit.c:967
__do_sys_exit_group kernel/exit.c:978 [inline]
__se_sys_exit_group kernel/exit.c:976 [inline]
__x64_sys_exit_group+0x3a/0x50 kernel/exit.c:976
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7f44e47bfad9
Code: Bad RIP value.
RSP: 002b:00007ffc33fe9988 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 00007f44e4836350 RCX: 00007f44e47bfad9
RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000001
RBP: 0000000000000001 R08: ffffffffffffffc0 R09: 00007f44e4830e40
R10: 000080001d00c0d0 R11: 0000000000000246 R12: 00007f44e4836350
R13: 0000000000000001 R14: 0000000000000000 R15: 0000000000000001
Modules linked in:
---[ end trace 133e3a03dcc5c5fc ]---
RIP: 0010:constant_test_bit arch/x86/include/asm/bitops.h:317 [inline]
RIP: 0010:set_buffer_uptodate include/linux/buffer_head.h:120 [inline]
RIP: 0010:do_journal_end+0x12cd/0x4840 fs/reiserfs/journal.c:4093
Code: 0f 85 cf 2b 00 00 48 8b 7b 18 b9 08 00 00 00 e8 79 c6 d9 ff 48 89 c2 48 89 44 24 78 48 b8 00 00 00 00 00 fc ff df 48 c1 ea 03 <80> 3c 02 00 0f 85 92 2b 00 00 4c 8b 74 24 78 31 ff 49 8b 1e 83 e3
RSP: 0018:ffff8880b1387a08 EFLAGS: 00010246
RAX: dffffc0000000000 RBX: ffffc90001b1a000 RCX: ffffffff81b0a8f6
RDX: 0000000000000000 RSI: ffffffff81b0ac88 RDI: 0000000000000005
RBP: ffff888089d25000 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: 0000000000000000
R13: 000000000000001e R14: ffff8880b1387b50 R15: ffffc90001b1a000
FS: 0000555555f01300(0000) GS:ffff8880ba100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fd4eb937000 CR3: 00000000aff9a000 CR4: 00000000003406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: 0f 85 cf 2b 00 00 jne 0x2bd5
6: 48 8b 7b 18 mov 0x18(%rbx),%rdi
a: b9 08 00 00 00 mov $0x8,%ecx
f: e8 79 c6 d9 ff callq 0xffd9c68d
14: 48 89 c2 mov %rax,%rdx
17: 48 89 44 24 78 mov %rax,0x78(%rsp)
1c: 48 b8 00 00 00 00 00 movabs $0xdffffc0000000000,%rax
23: fc ff df
26: 48 c1 ea 03 shr $0x3,%rdx
* 2a: 80 3c 02 00 cmpb $0x0,(%rdx,%rax,1) <-- trapping instruction
2e: 0f 85 92 2b 00 00 jne 0x2bc6
34: 4c 8b 74 24 78 mov 0x78(%rsp),%r14
39: 31 ff xor %edi,%edi
3b: 49 8b 1e mov (%r14),%rbx
3e: 83 .byte 0x83
3f: e3 .byte 0xe3


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