[v6.1] kernel BUG in txAbort (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 6741e066ec76 Linux 6.1.87
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13c34bab180000
kernel config: https://syzkaller.appspot.com/x/.config?x=5d37120947ebed5a
dashboard link: https://syzkaller.appspot.com/bug?extid=639de1efb7d0477096fa
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/e09aa9dab3c8/disk-6741e066.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/4176a4f5a4d5/vmlinux-6741e066.xz
kernel image: https://storage.googleapis.com/syzbot-assets/970367753980/Image-6741e066.gz.xz

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

read_mapping_page failed!
BUG at fs/jfs/jfs_txnmgr.c:2795 assert(mp->nohomeok)
------------[ cut here ]------------
kernel BUG at fs/jfs/jfs_txnmgr.c:2795!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 7682 Comm: syz-executor.4 Not tainted 6.1.87-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:2795 [inline]
pc : txAbort+0x56c/0x570 fs/jfs/jfs_txnmgr.c:2621
lr : LogSyncRelease fs/jfs/jfs_txnmgr.c:2795 [inline]
lr : txAbort+0x56c/0x570 fs/jfs/jfs_txnmgr.c:2621
sp : ffff80001e1e76d0
x29: ffff80001e1e7700 x28: 0000000000000000 x27: ffff0000cc7f5aa8
x26: ffff800019a34e44 x25: 0000000000000000 x24: dfff800000000000
x23: ffff800019a35000 x22: 0000000000000006 x21: ffff800015df3ae0
x20: ffff800019a35000 x19: 0000000000000048 x18: 1fffe0003686f176
x17: ffff80001584d000 x16: ffff80001215c9dc x15: ffff0001b4378bbc
x14: 1ffff00002b0a0b0 x13: dfff800000000000 x12: 0000000000000001
x11: 0000000000ff0100 x10: 0000000000000000 x9 : f21c4032bb3da600
x8 : f21c4032bb3da600 x7 : ffff80000827c8d4 x6 : 0000000000000000
x5 : 0000000000000080 x4 : 0000000000000001 x3 : ffff80000aa9158c
x2 : ffff0001b4378cd0 x1 : 0000000100000000 x0 : 0000000000000034
Call trace:
LogSyncRelease fs/jfs/jfs_txnmgr.c:2795 [inline]
txAbort+0x56c/0x570 fs/jfs/jfs_txnmgr.c:2621
txCommit+0x496c/0x5574 fs/jfs/jfs_txnmgr.c:1354
jfs_unlink+0x5b8/0xa20 fs/jfs/namei.c:555
vfs_unlink+0x2f0/0x508 fs/namei.c:4324
do_unlinkat+0x4cc/0x70c fs/namei.c:4392
__do_sys_unlinkat fs/namei.c:4435 [inline]
__se_sys_unlinkat fs/namei.c:4428 [inline]
__arm64_sys_unlinkat+0xcc/0xfc fs/namei.c:4428
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585
Code: b0046283 91348063 52815d62 959544f2 (d4210000)
---[ end trace 0000000000000000 ]---


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