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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 090666d3cc90 Linux 6.1.177
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12732cb9580000
kernel config: https://syzkaller.appspot.com/x/.config?x=cd374bd3b354feae
dashboard link: https://syzkaller.appspot.com/bug?extid=28402e3dbcc95bd93a75
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/378e2dbb7ed4/disk-090666d3.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/48878db70015/vmlinux-090666d3.xz
kernel image: https://storage.googleapis.com/syzbot-assets/31993c027dae/Image-090666d3.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+28402e...@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!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 PID: 15 Comm: ksoftirqd/0 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/02/2026
pstate: 624000c5 (nZCv daIF +PAN -UAO +TCO -DIT -SSBS BTYPE=--)
pc : lbmIODone+0x1280/0x12d4 fs/jfs/jfs_logmgr.c:2298
lr : lbmIODone+0x1280/0x12d4 fs/jfs/jfs_logmgr.c:2298
sp : ffff80001cb97a30
x29: ffff80001cb97a90 x28: 1fffe0001a7e8892 x27: ffff0000d3f44494
x26: 0000000000000000 x25: dfff800000000000 x24: 1fffe00019499c4f
x23: 0000000000000000 x22: 0000000000000020 x21: 0000000000000000
x20: 1fffe0001a594981 x19: ffff0000d2ca4c00 x18: 1fffe00033e7277e
x17: 0000000000000000 x16: ffff800011b8ee98 x15: 0000000000000000
x14: 0000000000000001 x13: 1ffff00003972eac x12: 0000000000000000
x11: ff00800008315174 x10: 0000000000000000 x9 : 7fc265625a934100
x8 : 7fc265625a934100 x7 : 0000000000000001 x6 : 0000000000000001
x5 : ffff80001cb974f8 x4 : ffff800015464e60 x3 : ffff80000a91ef3c
x2 : ffff00019f393d10 x1 : 0000000100000101 x0 : 000000000000003f
Call trace:
lbmIODone+0x1280/0x12d4 fs/jfs/jfs_logmgr.c:2298
bio_endio+0x750/0x794 block/bio.c:1554
req_bio_endio block/blk-mq.c:782 [inline]
blk_update_request+0x4ac/0xc58 block/blk-mq.c:927
blk_mq_end_request+0x54/0x8c block/blk-mq.c:1052
lo_complete_rq+0x1e8/0x238 drivers/block/loop.c:365
blk_complete_reqs block/blk-mq.c:1132 [inline]
blk_done_softirq+0x11c/0x168 block/blk-mq.c:1137
handle_softirqs+0x318/0xc90 kernel/softirq.c:596
run_ksoftirqd+0x7c/0x2ac kernel/softirq.c:968
smpboot_thread_fn+0x4e8/0x960 kernel/smpboot.c:164
kthread+0x254/0x2e0 kernel/kthread.c:376
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:850
Code: f0043b83 913f8063 52811f42 979cc303 (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