[v6.1] kernel BUG in lbmIODone

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 0a4a7855302d Linux 6.1.44
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=112034d7a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=5bbe2ab74b077c00
dashboard link: https://syzkaller.appspot.com/bug?extid=4a12b70830f28c6779d2
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/36307f1b9f72/disk-0a4a7855.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/8710647ab6be/vmlinux-0a4a7855.xz
kernel image: https://storage.googleapis.com/syzbot-assets/844b3bf8dbc9/bzImage-0a4a7855.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+4a12b7...@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 6.1.44-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/26/2023
RIP: 0010:lbmIODone+0x16f4/0x1750 fs/jfs/jfs_logmgr.c:2298
Code: 8b 81 7b 07 0f 0b e8 fb c0 82 fe 48 c7 c7 c0 7e 24 8b 48 c7 c6 c0 79 24 8b ba fa 08 00 00 48 c7 c1 20 88 24 8b e8 65 81 7b 07 <0f> 0b e8 d5 c0 82 fe 48 c7 c7 c0 7e 24 8b 48 c7 c6 c0 79 24 8b ba
RSP: 0018:ffffc900001b7ae0 EFLAGS: 00010046
RAX: 000000000000003f RBX: 0000000000000020 RCX: 188ac2d70c5db400
RDX: 0000000080000101 RSI: 0000000080000101 RDI: 0000000000000000
RBP: ffff888021dafb08 R08: ffffffff816db4cc R09: fffff52000036f15
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffff888021dafb00 R14: ffff88807d958a78 R15: 0000000000000246
FS: 0000000000000000(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 0000000023ee6000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
req_bio_endio block/blk-mq.c:763 [inline]
blk_update_request+0x53b/0x1010 block/blk-mq.c:908
blk_mq_end_request+0x3a/0x70 block/blk-mq.c:1035
blk_complete_reqs block/blk-mq.c:1113 [inline]
blk_done_softirq+0xf8/0x140 block/blk-mq.c:1118
__do_softirq+0x2e9/0xa4c kernel/softirq.c:571
run_ksoftirqd+0xc1/0x120 kernel/softirq.c:934
smpboot_thread_fn+0x51b/0xa10 kernel/smpboot.c:164
kthread+0x26e/0x300 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:lbmIODone+0x16f4/0x1750 fs/jfs/jfs_logmgr.c:2298
Code: 8b 81 7b 07 0f 0b e8 fb c0 82 fe 48 c7 c7 c0 7e 24 8b 48 c7 c6 c0 79 24 8b ba fa 08 00 00 48 c7 c1 20 88 24 8b e8 65 81 7b 07 <0f> 0b e8 d5 c0 82 fe 48 c7 c7 c0 7e 24 8b 48 c7 c6 c0 79 24 8b ba
RSP: 0018:ffffc900001b7ae0 EFLAGS: 00010046
RAX: 000000000000003f RBX: 0000000000000020 RCX: 188ac2d70c5db400
RDX: 0000000080000101 RSI: 0000000080000101 RDI: 0000000000000000
RBP: ffff888021dafb08 R08: ffffffff816db4cc R09: fffff52000036f15
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffff888021dafb00 R14: ffff88807d958a78 R15: 0000000000000246
FS: 0000000000000000(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 0000000023ee6000 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 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.