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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: e5cd595e23c1 Linux 6.1.83
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1799c4f9180000
kernel config: https://syzkaller.appspot.com/x/.config?x=99d0cbbc2b2c7cfd
dashboard link: https://syzkaller.appspot.com/bug?extid=e5701b0933e55e97f11b
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/cd28292a2eef/disk-e5cd595e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e8297fd856b2/vmlinux-e5cd595e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ea8c74634429/bzImage-e5cd595e.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+e5701b...@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: 0 PID: 15 Comm: ksoftirqd/0 Not tainted 6.1.83-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/29/2024
RIP: 0010:lbmIODone+0x16f4/0x1750 fs/jfs/jfs_logmgr.c:2298
Code: 2b b4 7e 07 0f 0b e8 6b 54 81 fe 48 c7 c7 80 b7 24 8b 48 c7 c6 80 b2 24 8b ba fa 08 00 00 48 c7 c1 e0 c0 24 8b e8 05 b4 7e 07 <0f> 0b e8 45 54 81 fe 48 c7 c7 80 b7 24 8b 48 c7 c6 80 b2 24 8b ba
RSP: 0018:ffffc90000147ae8 EFLAGS: 00010046
RAX: 000000000000003f RBX: 0000000000000020 RCX: e1c54ad6f22df500
RDX: 0000000080000101 RSI: 0000000080000101 RDI: 0000000000000000
RBP: ffff888017263208 R08: ffffffff816e1b2c R09: ffffed1017304f1c
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffff888017263200 R14: ffff888058c0da78 R15: 0000000000000246
FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f84a57ad988 CR3: 0000000076a86000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
req_bio_endio block/blk-mq.c:768 [inline]
blk_update_request+0x553/0x1040 block/blk-mq.c:913
blk_mq_end_request+0x3a/0x70 block/blk-mq.c:1040
blk_complete_reqs block/blk-mq.c:1118 [inline]
blk_done_softirq+0xf8/0x140 block/blk-mq.c:1123
__do_softirq+0x2e9/0xa4c kernel/softirq.c:571
run_ksoftirqd+0xc1/0x120 kernel/softirq.c:934
smpboot_thread_fn+0x52c/0xa30 kernel/smpboot.c:164
kthread+0x28d/0x320 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:307
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:lbmIODone+0x16f4/0x1750 fs/jfs/jfs_logmgr.c:2298
Code: 2b b4 7e 07 0f 0b e8 6b 54 81 fe 48 c7 c7 80 b7 24 8b 48 c7 c6 80 b2 24 8b ba fa 08 00 00 48 c7 c1 e0 c0 24 8b e8 05 b4 7e 07 <0f> 0b e8 45 54 81 fe 48 c7 c7 80 b7 24 8b 48 c7 c6 80 b2 24 8b ba
RSP: 0018:ffffc90000147ae8 EFLAGS: 00010046
RAX: 000000000000003f RBX: 0000000000000020 RCX: e1c54ad6f22df500
RDX: 0000000080000101 RSI: 0000000080000101 RDI: 0000000000000000
RBP: ffff888017263208 R08: ffffffff816e1b2c R09: ffffed1017304f1c
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffff888017263200 R14: ffff888058c0da78 R15: 0000000000000246
FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f84a57ad988 CR3: 0000000076a86000 CR4: 00000000003506f0
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