[v5.15] kernel BUG in reiserfs_in_journal

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 3299fb36854f Linux 5.15.108
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14c14bb8280000
kernel config: https://syzkaller.appspot.com/x/.config?x=7da5cf0bf5f17e50
dashboard link: https://syzkaller.appspot.com/bug?extid=e9217d81b538577e999d
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/e9dec7cd5a48/disk-3299fb36.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e054af719cf1/vmlinux-3299fb36.xz
kernel image: https://storage.googleapis.com/syzbot-assets/5ae902fb312f/Image-3299fb36.gz.xz

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

------------[ cut here ]------------
kernel BUG at fs/reiserfs/journal.c:505!
Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 4747 Comm: syz-executor.0 Not tainted 5.15.108-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/30/2023
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : reiserfs_in_journal+0x94c/0x950 fs/reiserfs/journal.c:505
lr : reiserfs_in_journal+0x94c/0x950 fs/reiserfs/journal.c:505
sp : ffff80001ebb6b20
x29: ffff80001ebb6b40 x28: ffff80001e259000 x27: 0000000000000000
x26: dfff800000000000 x25: ffff80001e279318 x24: ffff0001261344e0
x23: ffff80001a858048 x22: ffff80001a858050 x21: 0000000000000213
x20: ffff000131f0a678 x19: ffff000131f0a000 x18: 0000000000000000
x17: ff80800008c63770 x16: ffff8000082e7c9c x15: ffff800008c63770
x14: 0000000000000002 x13: ffffffffffffffff x12: 0000000000040000
x11: 0000000000016a02 x10: ffff80001d31a000 x9 : ffff800008cdbf48
x8 : 0000000000016a03 x7 : 0000000000000000 x6 : 0000000000000000
x5 : 0000000000000000 x4 : ffff80001ebb6c60 x3 : 0000000000000001
x2 : 0000000000000213 x1 : 0000000000000213 x0 : 0000000000000213
Call trace:
reiserfs_in_journal+0x94c/0x950 fs/reiserfs/journal.c:505
is_block_in_journal fs/reiserfs/bitmap.c:125 [inline]
scan_bitmap_block+0x3bc/0xdb0 fs/reiserfs/bitmap.c:203
scan_bitmap fs/reiserfs/bitmap.c:408 [inline]
allocate_without_wrapping_disk fs/reiserfs/bitmap.c:1161 [inline]
blocknrs_and_prealloc_arrays_from_search_start fs/reiserfs/bitmap.c:1274 [inline]
reiserfs_allocate_blocknrs+0x21a8/0x4264 fs/reiserfs/bitmap.c:1375
reiserfs_get_block+0x2580/0x3fd0 fs/reiserfs/inode.c:764
__block_write_begin_int+0x3ec/0x1608 fs/buffer.c:2012
__block_write_begin+0x40/0x54 fs/buffer.c:2062
reiserfs_write_begin+0x3c8/0x654 fs/reiserfs/inode.c:2790
generic_perform_write+0x24c/0x520 mm/filemap.c:3776
__generic_file_write_iter+0x230/0x454 mm/filemap.c:3903
generic_file_write_iter+0xb4/0x1b8 mm/filemap.c:3935
call_write_iter include/linux/fs.h:2103 [inline]
new_sync_write fs/read_write.c:507 [inline]
vfs_write+0x87c/0xb3c fs/read_write.c:594
ksys_write+0x15c/0x26c fs/read_write.c:647
__do_sys_write fs/read_write.c:659 [inline]
__se_sys_write fs/read_write.c:656 [inline]
__arm64_sys_write+0x7c/0x90 fs/read_write.c:656
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:596
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
Code: aa1603e0 97efa567 17ffff9d 97df8f4a (d4210000)
---[ end trace 512217a843c7604e ]---


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

syzbot has found a reproducer for the following issue on:

HEAD commit: f67653019430 Linux 5.15.118
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16b0c73f280000
kernel config: https://syzkaller.appspot.com/x/.config?x=717fa62bb7f0fe9

dashboard link: https://syzkaller.appspot.com/bug?extid=e9217d81b538577e999d
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=112a3c0b280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15343f0f280000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/d21188fbe046/disk-f6765301.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f0c688e23e63/vmlinux-f6765301.xz
kernel image: https://storage.googleapis.com/syzbot-assets/eca85b3bf72c/bzImage-f6765301.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/56623d9ebcf2/mount_0.gz

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

REISERFS (device loop0): Using r5 hash to sort names
REISERFS (device loop0): using 3.5.x disk format
REISERFS (device loop0): Created .reiserfs_priv - reserved for xattr storage.

------------[ cut here ]------------
kernel BUG at fs/reiserfs/journal.c:505!

invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 3497 Comm: syz-executor229 Not tainted 5.15.118-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/27/2023
RIP: 0010:reiserfs_in_journal+0xab6/0xac0 fs/reiserfs/journal.c:505
Code: f6 ff ff 48 8b 4c 24 30 80 e1 07 80 c1 03 38 c1 0f 8c 73 fe ff ff 48 8b 7c 24 30 e8 04 4a b9 ff e9 64 fe ff ff e8 9a ed 6f ff <0f> 0b 0f 1f 84 00 00 00 00 00 55 41 57 41 56 41 55 41 54 53 50 49
RSP: 0018:ffffc90002d7ee60 EFLAGS: 00010293
RAX: ffffffff82100cb6 RBX: ffffc90002d31048 RCX: ffff888078a9bb80
RDX: 0000000000000000 RSI: 0000000000000213 RDI: 0000000000000213
RBP: ffffc90002d31050 R08: ffffffff821004d2 R09: ffffed1002c39009
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000213
R13: ffff8880758ac000 R14: 1ffff1100eb158cf R15: dffffc0000000000
FS: 0000555555f8b300(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020002d30 CR3: 0000000023309000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
is_block_in_journal fs/reiserfs/bitmap.c:125 [inline]
scan_bitmap_block+0x2ec/0x1060 fs/reiserfs/bitmap.c:188

scan_bitmap fs/reiserfs/bitmap.c:408 [inline]
allocate_without_wrapping_disk fs/reiserfs/bitmap.c:1161 [inline]
blocknrs_and_prealloc_arrays_from_search_start fs/reiserfs/bitmap.c:1274 [inline]

reiserfs_allocate_blocknrs+0x2dd9/0x5070 fs/reiserfs/bitmap.c:1375
reiserfs_get_block+0x32b4/0x5390 fs/reiserfs/inode.c:764
__block_write_begin_int+0x60b/0x1650 fs/buffer.c:2012
reiserfs_write_begin+0x346/0x810 fs/reiserfs/inode.c:2790
generic_perform_write+0x2bf/0x5b0 mm/filemap.c:3776
__generic_file_write_iter+0x243/0x4f0 mm/filemap.c:3903
generic_file_write_iter+0xa7/0x1b0 mm/filemap.c:3935

call_write_iter include/linux/fs.h:2103 [inline]
new_sync_write fs/read_write.c:507 [inline]

vfs_write+0xacf/0xe50 fs/read_write.c:594
ksys_write+0x1a2/0x2c0 fs/read_write.c:647
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f1f982bba59
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 51 14 00 00 90 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 c0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffe25035198 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f1f982bba59
RDX: 0000000000000001 RSI: 0000000020000000 RDI: 0000000000000007
RBP: 00007f1f9827b2f0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f1f9827b380
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
</TASK>
Modules linked in:
---[ end trace fa93c36b0f721a9e ]---
RIP: 0010:reiserfs_in_journal+0xab6/0xac0 fs/reiserfs/journal.c:505
Code: f6 ff ff 48 8b 4c 24 30 80 e1 07 80 c1 03 38 c1 0f 8c 73 fe ff ff 48 8b 7c 24 30 e8 04 4a b9 ff e9 64 fe ff ff e8 9a ed 6f ff <0f> 0b 0f 1f 84 00 00 00 00 00 55 41 57 41 56 41 55 41 54 53 50 49
RSP: 0018:ffffc90002d7ee60 EFLAGS: 00010293
RAX: ffffffff82100cb6 RBX: ffffc90002d31048 RCX: ffff888078a9bb80
RDX: 0000000000000000 RSI: 0000000000000213 RDI: 0000000000000213
RBP: ffffc90002d31050 R08: ffffffff821004d2 R09: ffffed1002c39009
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000213
R13: ffff8880758ac000 R14: 1ffff1100eb158cf R15: dffffc0000000000
FS: 0000555555f8b300(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000056547a890bc0 CR3: 0000000023309000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


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