[syzbot] [jfs?] kernel BUG in txUpdateMap

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit:    2a8120d7b482 Merge tag 's390-6.10-2' of git://git.kernel.o..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=144e3042980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=5dd4fde1337a9e18
dashboard link: https://syzkaller.appspot.com/bug?extid=0a8a0b1abad0363db585
compiler:       gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: i386

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

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7bc7510fe41f/non_bootable_disk-2a8120d7.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/78c72ae6bdaf/vmlinux-2a8120d7.xz
kernel image: https://storage.googleapis.com/syzbot-assets/99dbb805b738/bzImage-2a8120d7.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+0a8a0b1abad0363db585@xxxxxxxxxxxxxxxxxxxxxxxxx

BUG at fs/jfs/jfs_txnmgr.c:2340 assert(mp->nohomeok == 1)
------------[ cut here ]------------
kernel BUG at fs/jfs/jfs_txnmgr.c:2340!
Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN NOPTI
CPU: 0 PID: 133 Comm: jfsCommit Not tainted 6.9.0-syzkaller-10713-g2a8120d7b482 #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
RIP: 0010:txUpdateMap+0xc8b/0xd20 fs/jfs/jfs_txnmgr.c:2340
Code: e9 5c f9 ff ff e8 d5 fd 82 fe 48 c7 c1 00 f4 6a 8b ba 24 09 00 00 48 c7 c6 80 e7 6a 8b 48 c7 c7 c0 e7 6a 8b e8 c6 9d 63 fe 90 <0f> 0b 48 89 df e8 7b 32 e0 fe e9 e1 f8 ff ff e8 31 33 e0 fe e9 a8
RSP: 0000:ffffc900020c7ce0 EFLAGS: 00010286
RAX: 0000000000000039 RBX: ffff88805f267580 RCX: ffffffff816f3519
RDX: 0000000000000000 RSI: ffffffff816fc096 RDI: 0000000000000005
RBP: 0000000000000002 R08: 0000000000000005 R09: 0000000000000000
R10: 0000000080000000 R11: 0000000000000000 R12: ffffc900022ea120
R13: 0000000000000001 R14: ffffc900022ea124 R15: dffffc0000000000
FS:  0000000000000000(0000) GS:ffff88802c000000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f76f6e2f760 CR3: 00000000294c0000 CR4: 0000000000350ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 txLazyCommit fs/jfs/jfs_txnmgr.c:2664 [inline]
 jfs_lazycommit+0x5e6/0xb20 fs/jfs/jfs_txnmgr.c:2733
 kthread+0x2c1/0x3a0 kernel/kthread.c:389
 ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:txUpdateMap+0xc8b/0xd20 fs/jfs/jfs_txnmgr.c:2340
Code: e9 5c f9 ff ff e8 d5 fd 82 fe 48 c7 c1 00 f4 6a 8b ba 24 09 00 00 48 c7 c6 80 e7 6a 8b 48 c7 c7 c0 e7 6a 8b e8 c6 9d 63 fe 90 <0f> 0b 48 89 df e8 7b 32 e0 fe e9 e1 f8 ff ff e8 31 33 e0 fe e9 a8
RSP: 0000:ffffc900020c7ce0 EFLAGS: 00010286
RAX: 0000000000000039 RBX: ffff88805f267580 RCX: ffffffff816f3519
RDX: 0000000000000000 RSI: ffffffff816fc096 RDI: 0000000000000005
RBP: 0000000000000002 R08: 0000000000000005 R09: 0000000000000000
R10: 0000000080000000 R11: 0000000000000000 R12: ffffc900022ea120
R13: 0000000000000001 R14: ffffc900022ea124 R15: dffffc0000000000
FS:  0000000000000000(0000) GS:ffff88802c100000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f7a37f24488 CR3: 00000000294c0000 CR4: 0000000000350ef0
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 syzkaller@xxxxxxxxxxxxxxxx.

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