[v5.15] kernel BUG in txAbort

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: b925f60c6ee7 Linux 5.15.157
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=127eee9b180000
kernel config: https://syzkaller.appspot.com/x/.config?x=802c8e49b2826f05
dashboard link: https://syzkaller.appspot.com/bug?extid=dccc2d773ba9904db8ea
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/add896a77889/disk-b925f60c.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e24f83a46999/vmlinux-b925f60c.xz
kernel image: https://storage.googleapis.com/syzbot-assets/de040a426c29/Image-b925f60c.gz.xz

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

read_mapping_page failed!
BUG at fs/jfs/jfs_txnmgr.c:2829 assert(mp->nohomeok)
------------[ cut here ]------------
kernel BUG at fs/jfs/jfs_txnmgr.c:2829!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 4118 Comm: syz-executor.1 Not tainted 5.15.157-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
pstate: 60401005 (nZCv daif +PAN -UAO -TCO -DIT +SSBS BTYPE=--)
pc : LogSyncRelease fs/jfs/jfs_txnmgr.c:2829 [inline]
pc : txAbort+0x56c/0x570 fs/jfs/jfs_txnmgr.c:2655
lr : LogSyncRelease fs/jfs/jfs_txnmgr.c:2829 [inline]
lr : txAbort+0x56c/0x570 fs/jfs/jfs_txnmgr.c:2655
sp : ffff80001d6f7610
x29: ffff80001d6f7640 x28: 0000000000000000 x27: ffff0000eb04e000
x26: ffff800018583c24 x25: 0000000000000000 x24: dfff800000000000
x23: ffff800018583000 x22: 0000000000000008 x21: ffff800014e9f680
x20: ffff800018583000 x19: 0000000000000048 x18: 0000000000000001
x17: 0000000000000002 x16: ffff800011997d7c x15: 00000000ffffffff
x14: ffff0000c8161b40 x13: 0000000000000001 x12: 0000000000040000
x11: 0000000000009ecf x10: ffff80001d1e9000 x9 : f49b278ace55d200
x8 : f49b278ace55d200 x7 : 0000000000000001 x6 : 0000000000000001
x5 : ffff80001d6f6d78 x4 : ffff800014a1f7c0 x3 : ffff800008550224
x2 : 0000000000000001 x1 : 0000000100000000 x0 : 0000000000000034
Call trace:
LogSyncRelease fs/jfs/jfs_txnmgr.c:2829 [inline]
txAbort+0x56c/0x570 fs/jfs/jfs_txnmgr.c:2655
txCommit+0x49a8/0x55b0 fs/jfs/jfs_txnmgr.c:1354
jfs_create+0x828/0xa1c fs/jfs/namei.c:156
vfs_create+0x2cc/0x434 fs/namei.c:3162
do_mknodat+0x314/0x694 fs/namei.c:3994
__do_sys_mknodat fs/namei.c:4022 [inline]
__se_sys_mknodat fs/namei.c:4019 [inline]
__arm64_sys_mknodat+0xb0/0xcc fs/namei.c:4019
__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:608
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
Code: f00429a3 91010063 528161a2 959828f0 (d4210000)
---[ end trace 4425e0dcdf04ded7 ]---


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

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

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

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