[syzbot] kernel BUG in lbmIODone

[syzbot <syzbot+52ddb6c83a04ca55f975@syzkaller.appspotmail.com>]

Hello,

syzbot found the following issue on:

HEAD commit:    a763d5a5abd6 Merge tag 'scsi-fixes' of git://git.kernel.or..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14556c83b00000
kernel config:  https://syzkaller.appspot.com/x/.config?x=5247c9e141823545
dashboard link: https://syzkaller.appspot.com/bug?extid=52ddb6c83a04ca55f975
compiler:       gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2

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

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+52ddb6c83a04ca55f975@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: 13 Comm: ksoftirqd/0 Not tainted 5.16.0-rc4-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:lbmIODone.cold+0xc9/0x116 fs/jfs/jfs_logmgr.c:2313
Code: 68 c3 b3 f8 eb d3 e8 31 89 6d f8 48 c7 c1 e0 8a e6 89 ba 09 09 00 00 48 c7 c6 20 89 e6 89 48 c7 c7 60 89 e6 89 e8 ec 12 f8 ff <0f> 0b e8 0b 89 6d f8 48 c7 c1 20 8b e6 89 ba 0a 09 00 00 48 c7 c6
RSP: 0018:ffffc90000f3fc88 EFLAGS: 00010082
RAX: 000000000000003f RBX: ffff8880208bf100 RCX: 0000000000000000
RDX: ffff888011c86040 RSI: ffffffff815e52a8 RDI: fffff520001e7f83
RBP: 0000000000000020 R08: 000000000000003f R09: 0000000000000000
R10: ffffffff815df04e R11: 0000000000000000 R12: 0000000000000246
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f3fa25ed000 CR3: 00000000412c7000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 bio_endio+0x5ec/0x770 block/bio.c:1489
 req_bio_endio block/blk-mq.c:674 [inline]
 blk_update_request+0x46a/0x1400 block/blk-mq.c:742
 blk_mq_end_request+0x4b/0x80 block/blk-mq.c:821
 lo_complete_rq+0x1c2/0x280 drivers/block/loop.c:369
 blk_complete_reqs+0xad/0xe0 block/blk-mq.c:892
 __do_softirq+0x29b/0x9c2 kernel/softirq.c:558
 run_ksoftirqd kernel/softirq.c:921 [inline]
 run_ksoftirqd+0x2d/0x60 kernel/softirq.c:913
 smpboot_thread_fn+0x645/0x9c0 kernel/smpboot.c:164
 kthread+0x405/0x4f0 kernel/kthread.c:327
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
 </TASK>
Modules linked in:
---[ end trace 7200a80d946f066f ]---
RIP: 0010:lbmIODone.cold+0xc9/0x116 fs/jfs/jfs_logmgr.c:2313
Code: 68 c3 b3 f8 eb d3 e8 31 89 6d f8 48 c7 c1 e0 8a e6 89 ba 09 09 00 00 48 c7 c6 20 89 e6 89 48 c7 c7 60 89 e6 89 e8 ec 12 f8 ff <0f> 0b e8 0b 89 6d f8 48 c7 c1 20 8b e6 89 ba 0a 09 00 00 48 c7 c6
RSP: 0018:ffffc90000f3fc88 EFLAGS: 00010082
RAX: 000000000000003f RBX: ffff8880208bf100 RCX: 0000000000000000
RDX: ffff888011c86040 RSI: ffffffff815e52a8 RDI: fffff520001e7f83
RBP: 0000000000000020 R08: 000000000000003f R09: 0000000000000000
R10: ffffffff815df04e R11: 0000000000000000 R12: 0000000000000246
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f3fa25ed000 CR3: 00000000412c7000 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 syzkaller@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.