[v6.1] kernel BUG in lbmIODone (4)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: bec0e10ee67e Linux 6.1.160
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1619439a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=6a5cbd268406bf43
dashboard link: https://syzkaller.appspot.com/bug?extid=3fcd00ba75eb8f87da22
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/ddf82d415346/disk-bec0e10e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/11536559ad07/vmlinux-bec0e10e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/fba42d912db2/bzImage-bec0e10e.xz

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

BUG at fs/jfs/jfs_logmgr.c:2298 assert(bp->l_flag & lbmRELEASE)
------------[ cut here ]------------
kernel BUG at fs/jfs/jfs_logmgr.c:2298!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 21 Comm: ksoftirqd/1 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
RIP: 0010:lbmIODone+0x1622/0x1670 fs/jfs/jfs_logmgr.c:2298
Code: 54 02 18 07 0f 0b e8 fd e5 92 fe 48 c7 c7 a0 2d a6 8a 48 c7 c6 a0 28 a6 8a ba fa 08 00 00 48 c7 c1 20 37 a6 8a e8 2e 02 18 07 <0f> 0b e8 d7 e5 92 fe 48 c7 c7 a0 2d a6 8a 48 c7 c6 a0 28 a6 8a ba
RSP: 0018:ffffc900001b7ab8 EFLAGS: 00010046
RAX: 000000000000003f RBX: 0000000000000020 RCX: 4a2a1e17350d0500
RDX: 0000000000000100 RSI: 0000000080000101 RDI: 0000000000000000
RBP: ffff888019654c08 R08: dffffc0000000000 R09: fffff52000036ef9
R10: fffff52000036ef9 R11: 1ffff92000036ef8 R12: ffff888019654c00
R13: dffffc0000000000 R14: 0000000000000a06 R15: ffff8880552a4a78
FS: 0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f4593372a60 CR3: 000000005ce00000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
req_bio_endio block/blk-mq.c:782 [inline]
blk_update_request+0x593/0xe30 block/blk-mq.c:927
blk_mq_end_request+0x3a/0x70 block/blk-mq.c:1052
blk_complete_reqs block/blk-mq.c:1132 [inline]
blk_done_softirq+0x100/0x150 block/blk-mq.c:1137
handle_softirqs+0x2a1/0x920 kernel/softirq.c:596
run_ksoftirqd+0x98/0xf0 kernel/softirq.c:968
smpboot_thread_fn+0x64a/0xa40 kernel/smpboot.c:164
kthread+0x29d/0x330 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:lbmIODone+0x1622/0x1670 fs/jfs/jfs_logmgr.c:2298
Code: 54 02 18 07 0f 0b e8 fd e5 92 fe 48 c7 c7 a0 2d a6 8a 48 c7 c6 a0 28 a6 8a ba fa 08 00 00 48 c7 c1 20 37 a6 8a e8 2e 02 18 07 <0f> 0b e8 d7 e5 92 fe 48 c7 c7 a0 2d a6 8a 48 c7 c6 a0 28 a6 8a ba
RSP: 0018:ffffc900001b7ab8 EFLAGS: 00010046
RAX: 000000000000003f RBX: 0000000000000020 RCX: 4a2a1e17350d0500
RDX: 0000000000000100 RSI: 0000000080000101 RDI: 0000000000000000
RBP: ffff888019654c08 R08: dffffc0000000000 R09: fffff52000036ef9
R10: fffff52000036ef9 R11: 1ffff92000036ef8 R12: ffff888019654c00
R13: dffffc0000000000 R14: 0000000000000a06 R15: ffff8880552a4a78
FS: 0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f4593372a60 CR3: 000000005ce00000 CR4: 00000000003506e0
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 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