[jfs?] [fat?] general protection fault in txEnd

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: c4215ee4771b Linux 4.14.302
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15bae73c480000
kernel config: https://syzkaller.appspot.com/x/.config?x=4a9988fe055c9527
dashboard link: https://syzkaller.appspot.com/bug?extid=dfc3f2bb5e696bc45f18
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14783388480000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11fb5832480000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c93ba055d204/disk-c4215ee4.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/bfbc929a33c1/vmlinux-c4215ee4.xz
kernel image: https://storage.googleapis.com/syzbot-assets/444658051770/bzImage-c4215ee4.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/255fc2b3d592/mount_0.gz

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

IPv6: ADDRCONF(NETDEV_CHANGE): batadv_slave_1: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): veth1_to_batadv: link becomes ready
ERROR: (device loop0): txAbort:
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
Modules linked in:
CPU: 0 PID: 8223 Comm: syz-executor418 Not tainted 4.14.302-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
task: ffff8880b022a280 task.stack: ffff888099848000
RIP: 0010:txEnd+0x148/0x2d0 fs/jfs/jfs_txnmgr.c:547
RSP: 0018:ffff88809984fb40 EFLAGS: 00010203
RAX: dffffc0000000000 RBX: ffffc900013b8100 RCX: 0000000000000000
RDX: 0000000000000026 RSI: ffff8880b022ab58 RDI: 0000000000000134
RBP: 0000000000000000 R08: ffffc900013b8150 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000001
R13: ffffc900013b8102 R14: ffff88808b0814a8 R15: ffff88808b0814c4
FS: 00007fba67c7c700(0000) GS:ffff8880ba400000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fba6f09e000 CR3: 00000000b611a000 CR4: 00000000003406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
add_missing_indices fs/jfs/jfs_dtree.c:2968 [inline]
jfs_readdir+0x22c1/0x36c0 fs/jfs/jfs_dtree.c:3314
iterate_dir+0x478/0x5e0 fs/readdir.c:54
SYSC_getdents fs/readdir.c:272 [inline]
SyS_getdents+0x125/0x240 fs/readdir.c:253
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x5e/0xd3
RIP: 0033:0x7fba6f8fdfe9
RSP: 002b:00007fba67c7c208 EFLAGS: 00000246 ORIG_RAX: 000000000000004e
RAX: ffffffffffffffda RBX: 00007fba6f982798 RCX: 00007fba6f8fdfe9
RDX: 000000000000004c RSI: 0000000020000100 RDI: 0000000000000004
RBP: 00007fba6f982790 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fba6f98279c
R13: 00007ffe3459b99f R14: 00007fba67c7c300 R15: 0000000000022000
Code: 05 fe 22 b7 09 41 0f b7 fc 89 3d f4 22 b7 09 48 8d bd 34 01 00 00 48 89 fa 48 c1 ea 03 66 89 43 28 48 b8 00 00 00 00 00 fc ff df <0f> b6 14 02 48 89 f8 83 e0 07 83 c0 03 38 d0 7c 08 84 d2 0f 85
RIP: txEnd+0x148/0x2d0 fs/jfs/jfs_txnmgr.c:547 RSP: ffff88809984fb40
---[ end trace ee44a511df0fd863 ]---
----------------
Code disassembly (best guess):
0: 05 fe 22 b7 09 add $0x9b722fe,%eax
5: 41 0f b7 fc movzwl %r12w,%edi
9: 89 3d f4 22 b7 09 mov %edi,0x9b722f4(%rip) # 0x9b72303
f: 48 8d bd 34 01 00 00 lea 0x134(%rbp),%rdi
16: 48 89 fa mov %rdi,%rdx
19: 48 c1 ea 03 shr $0x3,%rdx
1d: 66 89 43 28 mov %ax,0x28(%rbx)
21: 48 b8 00 00 00 00 00 movabs $0xdffffc0000000000,%rax
28: fc ff df
* 2b: 0f b6 14 02 movzbl (%rdx,%rax,1),%edx <-- trapping instruction
2f: 48 89 f8 mov %rdi,%rax
32: 83 e0 07 and $0x7,%eax
35: 83 c0 03 add $0x3,%eax
38: 38 d0 cmp %dl,%al
3a: 7c 08 jl 0x44
3c: 84 d2 test %dl,%dl
3e: 0f .byte 0xf
3f: 85 .byte 0x85


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