[v5.15] kernel BUG in lbmIODone (3)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: c52b9710c83d Linux 5.15.156
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=123794ef180000
kernel config: https://syzkaller.appspot.com/x/.config?x=567b6ddc38438433
dashboard link: https://syzkaller.appspot.com/bug?extid=4d4c0afca08901689c95
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/1bd4b9969373/disk-c52b9710.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/10509e89bd25/vmlinux-c52b9710.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a623a4c52eb5/bzImage-c52b9710.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+4d4c0a...@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: 1 PID: 20 Comm: ksoftirqd/1 Not tainted 5.15.156-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
RIP: 0010:lbmIODone+0x16f4/0x1750 fs/jfs/jfs_logmgr.c:2313
Code: c2 f3 36 07 0f 0b e8 cb dd 9a fe 48 c7 c7 c0 5e c1 8a 48 c7 c6 c0 59 c1 8a ba 09 09 00 00 48 c7 c1 20 68 c1 8a e8 9c f3 36 07 <0f> 0b e8 a5 dd 9a fe 48 c7 c7 c0 5e c1 8a 48 c7 c6 c0 59 c1 8a ba
RSP: 0018:ffffc90000da7b00 EFLAGS: 00010046
RAX: 000000000000003f RBX: 0000000000000020 RCX: 09f731b45a630700
RDX: 0000000080000101 RSI: 0000000080000101 RDI: 0000000000000000
RBP: ffff88801e61f408 R08: ffffffff8166862c R09: ffffed10173667a8
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffff88801e61f400 R14: ffff888074049278 R15: 0000000000000246
FS: 0000000000000000(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffd9c6dafa8 CR3: 000000006181d000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
req_bio_endio block/blk-core.c:261 [inline]
blk_update_request+0x87c/0x1470 block/blk-core.c:1441
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:921
smpboot_thread_fn+0x51b/0x9d0 kernel/smpboot.c:164
kthread+0x3f6/0x4f0 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:300
</TASK>
Modules linked in:
---[ end trace 09f12a191550ee46 ]---
RIP: 0010:lbmIODone+0x16f4/0x1750 fs/jfs/jfs_logmgr.c:2313
Code: c2 f3 36 07 0f 0b e8 cb dd 9a fe 48 c7 c7 c0 5e c1 8a 48 c7 c6 c0 59 c1 8a ba 09 09 00 00 48 c7 c1 20 68 c1 8a e8 9c f3 36 07 <0f> 0b e8 a5 dd 9a fe 48 c7 c7 c0 5e c1 8a 48 c7 c6 c0 59 c1 8a ba
RSP: 0018:ffffc90000da7b00 EFLAGS: 00010046
RAX: 000000000000003f RBX: 0000000000000020 RCX: 09f731b45a630700
RDX: 0000000080000101 RSI: 0000000080000101 RDI: 0000000000000000
RBP: ffff88801e61f408 R08: ffffffff8166862c R09: ffffed10173667a8
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffff88801e61f400 R14: ffff888074049278 R15: 0000000000000246
FS: 0000000000000000(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffd9c6dafa8 CR3: 000000006181d000 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