[v5.15] kernel BUG in txEnd

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 38d4ca22a528 Linux 5.15.124
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=123bdb13a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=45eb463798d34fdb
dashboard link: https://syzkaller.appspot.com/bug?extid=914c3cb75ef219729a2e
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17fee979a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15854533a80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/0470c022da0e/disk-38d4ca22.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/56cf48a83529/vmlinux-38d4ca22.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ac8ac64c33ec/bzImage-38d4ca22.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/10e828f858c2/mount_0.gz

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

loop0: detected capacity change from 0 to 32768
ERROR: (device loop0): xtTruncate: XT_GETPAGE: xtree page corrupt
ERROR: (device loop0): remounting filesystem as read-only
BUG at fs/jfs/jfs_txnmgr.c:528 assert(tblk->next == 0)
------------[ cut here ]------------
kernel BUG at fs/jfs/jfs_txnmgr.c:528!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 3500 Comm: syz-executor368 Not tainted 5.15.124-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2023
RIP: 0010:txEnd+0x552/0x560 fs/jfs/jfs_txnmgr.c:528
Code: fe e9 cd fe ff ff e8 8d 76 9c fe 48 c7 c7 c0 ef c0 8a 48 c7 c6 b9 eb c0 8a ba 10 02 00 00 48 c7 c1 00 f0 c0 8a e8 27 67 37 07 <0f> 0b 66 2e 0f 1f 84 00 00 00 00 00 66 90 55 41 57 41 56 41 55 41
RSP: 0018:ffffc90002def5b0 EFLAGS: 00010246
RAX: 0000000000000036 RBX: 0000000000000001 RCX: 4464bfddbfa9ab00
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: 1ffff92000470227 R08: ffffffff816649cc R09: fffff520005bddf5
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: 0000000000000001 R14: ffffc90002381138 R15: 0000000000000110
FS: 0000555556242380(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020000040 CR3: 0000000022da8000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
jfs_truncate_nolock+0x2ef/0x380 fs/jfs/inode.c:402
jfs_truncate+0xc7/0x140 fs/jfs/inode.c:423
jfs_setattr+0x44a/0x670 fs/jfs/file.c:119
notify_change+0xd4d/0x1000 fs/attr.c:488
do_truncate+0x21c/0x300 fs/open.c:65
handle_truncate fs/namei.c:3195 [inline]
do_open fs/namei.c:3542 [inline]
path_openat+0x28a0/0x2f20 fs/namei.c:3672
do_filp_open+0x21c/0x460 fs/namei.c:3699
do_sys_openat2+0x13b/0x500 fs/open.c:1211
do_sys_open fs/open.c:1227 [inline]
__do_sys_open fs/open.c:1235 [inline]
__se_sys_open fs/open.c:1231 [inline]
__x64_sys_open+0x221/0x270 fs/open.c:1231
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:0x7ff3c06835f9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 61 17 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fffc1389d58 EFLAGS: 00000246 ORIG_RAX: 0000000000000002
RAX: ffffffffffffffda RBX: 00007fffc1389f38 RCX: 00007ff3c06835f9
RDX: 0000000000000000 RSI: 000000000014527e RDI: 0000000020000040
RBP: 00007ff3c06fc610 R08: 0000000000005dea R09: 0000000000000000
R10: 00007fffc1389c20 R11: 0000000000000246 R12: 0000000000000001
R13: 00007fffc1389f28 R14: 0000000000000001 R15: 0000000000000001
</TASK>
Modules linked in:
---[ end trace 8f6e2f7f524e190a ]---
RIP: 0010:txEnd+0x552/0x560 fs/jfs/jfs_txnmgr.c:528
Code: fe e9 cd fe ff ff e8 8d 76 9c fe 48 c7 c7 c0 ef c0 8a 48 c7 c6 b9 eb c0 8a ba 10 02 00 00 48 c7 c1 00 f0 c0 8a e8 27 67 37 07 <0f> 0b 66 2e 0f 1f 84 00 00 00 00 00 66 90 55 41 57 41 56 41 55 41
RSP: 0018:ffffc90002def5b0 EFLAGS: 00010246
RAX: 0000000000000036 RBX: 0000000000000001 RCX: 4464bfddbfa9ab00
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: 1ffff92000470227 R08: ffffffff816649cc R09: fffff520005bddf5
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: 0000000000000001 R14: ffffc90002381138 R15: 0000000000000110
FS: 0000555556242380(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020000040 CR3: 0000000022da8000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


---
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 bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

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.

If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup