[v6.6] kernel BUG in txUnlock

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 6282921b6825 Linux 6.6.94
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12e1830c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=96da6b2210cda427
dashboard link: https://syzkaller.appspot.com/bug?extid=4d1764d69ed762160c10
compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a3bf0d8e22b2/disk-6282921b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d1d442f782d0/vmlinux-6282921b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a8378f4b7e1b/bzImage-6282921b.xz

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

BUG at fs/jfs/jfs_txnmgr.c:931 assert(mp->nohomeok > 0)
------------[ cut here ]------------
kernel BUG at fs/jfs/jfs_txnmgr.c:931!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 112 Comm: jfsCommit Not tainted 6.6.94-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:txUnlock+0xc87/0xcb0 fs/jfs/jfs_txnmgr.c:931
Code: 5f d8 58 07 0f 0b e8 28 83 83 fe 48 c7 c7 80 14 e4 8a 48 c7 c6 79 10 e4 8a ba a3 03 00 00 48 c7 c1 60 21 e4 8a e8 39 d8 58 07 <0f> 0b e8 02 83 83 fe 48 c7 c7 80 14 e4 8a 48 c7 c6 79 10 e4 8a ba
RSP: 0018:ffffc90002d47d08 EFLAGS: 00010246
RAX: 0000000000000037 RBX: 0000000000001000 RCX: 05b86751d550ad00
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffffc900028ba750 R08: ffffc90002d47907 R09: 1ffff920005a8f20
R10: dffffc0000000000 R11: fffff520005a8f21 R12: ffff888026acf6c8
R13: dffffc0000000000 R14: 0000000000000000 R15: ffff8880532aee94
FS: 0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffde2db4000 CR3: 000000007d3de000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
txLazyCommit fs/jfs/jfs_txnmgr.c:2682 [inline]
jfs_lazycommit+0x570/0xa60 fs/jfs/jfs_txnmgr.c:2732
kthread+0x2fa/0x390 kernel/kthread.c:388
ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:txUnlock+0xc87/0xcb0 fs/jfs/jfs_txnmgr.c:931
Code: 5f d8 58 07 0f 0b e8 28 83 83 fe 48 c7 c7 80 14 e4 8a 48 c7 c6 79 10 e4 8a ba a3 03 00 00 48 c7 c1 60 21 e4 8a e8 39 d8 58 07 <0f> 0b e8 02 83 83 fe 48 c7 c7 80 14 e4 8a 48 c7 c6 79 10 e4 8a ba
RSP: 0018:ffffc90002d47d08 EFLAGS: 00010246
RAX: 0000000000000037 RBX: 0000000000001000 RCX: 05b86751d550ad00
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffffc900028ba750 R08: ffffc90002d47907 R09: 1ffff920005a8f20
R10: dffffc0000000000 R11: fffff520005a8f21 R12: ffff888026acf6c8
R13: dffffc0000000000 R14: 0000000000000000 R15: ffff8880532aee94
FS: 0000000000000000(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fcc10180ab8 CR3: 000000000cb30000 CR4: 00000000003506f0


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

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: 6282921b6825 Linux 6.6.94
git tree: linux-6.6.y

console output: https://syzkaller.appspot.com/x/log.txt?x=11ee4dd4580000

kernel config: https://syzkaller.appspot.com/x/.config?x=96da6b2210cda427
dashboard link: https://syzkaller.appspot.com/bug?extid=4d1764d69ed762160c10
compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15ee4dd4580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14b5330c580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a3bf0d8e22b2/disk-6282921b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d1d442f782d0/vmlinux-6282921b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a8378f4b7e1b/bzImage-6282921b.xz

mounted in repro: https://storage.googleapis.com/syzbot-assets/01db828ade78/mount_0.gz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=1139f6bc580000)

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

BUG at fs/jfs/jfs_txnmgr.c:931 assert(mp->nohomeok > 0)
------------[ cut here ]------------
kernel BUG at fs/jfs/jfs_txnmgr.c:931!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN

CPU: 0 PID: 111 Comm: jfsCommit Not tainted 6.6.94-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:txUnlock+0xc87/0xcb0 fs/jfs/jfs_txnmgr.c:931
Code: 5f d8 58 07 0f 0b e8 28 83 83 fe 48 c7 c7 80 14 e4 8a 48 c7 c6 79 10 e4 8a ba a3 03 00 00 48 c7 c1 60 21 e4 8a e8 39 d8 58 07 <0f> 0b e8 02 83 83 fe 48 c7 c7 80 14 e4 8a 48 c7 c6 79 10 e4 8a ba

RSP: 0018:ffffc90002ca7d08 EFLAGS: 00010246
RAX: 0000000000000037 RBX: 0000000000001000 RCX: 4e55a7866e378e00

RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000

RBP: ffffc9000281a1b0 R08: ffffc90002ca7a07 R09: 1ffff92000594f40
R10: dffffc0000000000 R11: fffff52000594f41 R12: ffff888024ece4d8
R13: dffffc0000000000 R14: 0000000000000000 R15: ffff888020e50694

FS: 0000000000000000(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

CR2: 00007f30861aa000 CR3: 000000007b926000 CR4: 00000000003506f0

DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
txLazyCommit fs/jfs/jfs_txnmgr.c:2682 [inline]
jfs_lazycommit+0x570/0xa60 fs/jfs/jfs_txnmgr.c:2732
kthread+0x2fa/0x390 kernel/kthread.c:388
ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:txUnlock+0xc87/0xcb0 fs/jfs/jfs_txnmgr.c:931
Code: 5f d8 58 07 0f 0b e8 28 83 83 fe 48 c7 c7 80 14 e4 8a 48 c7 c6 79 10 e4 8a ba a3 03 00 00 48 c7 c1 60 21 e4 8a e8 39 d8 58 07 <0f> 0b e8 02 83 83 fe 48 c7 c7 80 14 e4 8a 48 c7 c6 79 10 e4 8a ba

RSP: 0018:ffffc90002ca7d08 EFLAGS: 00010246
RAX: 0000000000000037 RBX: 0000000000001000 RCX: 4e55a7866e378e00

RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000

RBP: ffffc9000281a1b0 R08: ffffc90002ca7a07 R09: 1ffff92000594f40
R10: dffffc0000000000 R11: fffff52000594f41 R12: ffff888024ece4d8
R13: dffffc0000000000 R14: 0000000000000000 R15: ffff888020e50694

FS: 0000000000000000(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

CR2: 00005606b1ee8168 CR3: 000000002db29000 CR4: 00000000003506f0

DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400

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