[v5.15] kernel BUG in lbmIODone

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: b0ece631f84a Linux 5.15.111
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=177fc0fa280000
kernel config: https://syzkaller.appspot.com/x/.config?x=5e93479ceb1e500
dashboard link: https://syzkaller.appspot.com/bug?extid=a02ab4f5d800dfa67163
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/4dbb092b5601/disk-b0ece631.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/5fe7e3edcf9b/vmlinux-b0ece631.xz
kernel image: https://storage.googleapis.com/syzbot-assets/1b2e75f47bfb/bzImage-b0ece631.xz

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

BUG at fs/jfs/jfs_logmgr.c:2313 assert(bp->l_flag & lbmRELEASE)
------------[ cut here ]------------
kernel BUG at fs/jfs/jfs_logmgr.c:2313!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 14 Comm: ksoftirqd/0 Not tainted 5.15.111-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/28/2023
RIP: 0010:lbmIODone+0x16f4/0x1750 fs/jfs/jfs_logmgr.c:2313
Code: 9b 09 36 07 0f 0b e8 bb ba 9c fe 48 c7 c7 c0 d2 c0 8a 48 c7 c6 c0 cd c0 8a ba 09 09 00 00 48 c7 c1 20 dc c0 8a e8 75 09 36 07 <0f> 0b e8 95 ba 9c fe 48 c7 c7 c0 d2 c0 8a 48 c7 c6 c0 cd c0 8a ba
RSP: 0018:ffffc90000d37b00 EFLAGS: 00010046
RAX: 000000000000003f RBX: 0000000000000020 RCX: de78acef8cba9c00
RDX: 0000000080000101 RSI: 0000000080000101 RDI: 0000000000000000
RBP: ffff888033982508 R08: ffffffff8166341c R09: ffffed10173467a0
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffff888033982500 R14: ffff888016bc4278 R15: 0000000000000246
FS: 0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2f421000 CR3: 0000000077ca7000 CR4: 00000000003506f0
Call Trace:
<TASK>
req_bio_endio block/blk-core.c:261 [inline]
blk_update_request+0x87c/0x1470 block/blk-core.c:1447
blk_mq_end_request+0x3a/0x70 block/blk-mq.c:575
blk_complete_reqs block/blk-mq.c:587 [inline]
blk_done_softirq+0xf2/0x130 block/blk-mq.c:592
__do_softirq+0x3b3/0x93a kernel/softirq.c:558
run_ksoftirqd+0xc1/0x120 kernel/softirq.c:920
smpboot_thread_fn+0x51b/0x9d0 kernel/smpboot.c:164
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</TASK>
Modules linked in:
---[ end trace 1811310ced1eac69 ]---
RIP: 0010:lbmIODone+0x16f4/0x1750 fs/jfs/jfs_logmgr.c:2313
Code: 9b 09 36 07 0f 0b e8 bb ba 9c fe 48 c7 c7 c0 d2 c0 8a 48 c7 c6 c0 cd c0 8a ba 09 09 00 00 48 c7 c1 20 dc c0 8a e8 75 09 36 07 <0f> 0b e8 95 ba 9c fe 48 c7 c7 c0 d2 c0 8a 48 c7 c6 c0 cd c0 8a ba
RSP: 0018:ffffc90000d37b00 EFLAGS: 00010046
RAX: 000000000000003f RBX: 0000000000000020 RCX: de78acef8cba9c00
RDX: 0000000080000101 RSI: 0000000080000101 RDI: 0000000000000000
RBP: ffff888033982508 R08: ffffffff8166341c R09: ffffed10173467a0
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffff888033982500 R14: ffff888016bc4278 R15: 0000000000000246
FS: 0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2f421000 CR3: 0000000077ca7000 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 bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.