kernel BUG at fs/jfs/jfs_logmgr.c:LINE!

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: cbfa1702 Linux 4.14.198
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1647704b900000
kernel config: https://syzkaller.appspot.com/x/.config?x=3990958d85b55e59
dashboard link: https://syzkaller.appspot.com/bug?extid=0f462d91a4a5f8befb20
compiler: gcc (GCC) 10.1.0-syz 20200507

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+0f462d...@syzkaller.appspotmail.com

(syz-executor.2,8025,0):ocfs2_fill_super:1217 ERROR: status = -22
BUG at fs/jfs/jfs_logmgr.c:2325 assert(bp->l_flag & lbmRELEASE)
------------[ cut here ]------------
kernel BUG at fs/jfs/jfs_logmgr.c:2325!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
Modules linked in:
CPU: 1 PID: 8039 Comm: loop5 Not tainted 4.14.198-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
task: ffff8880603f03c0 task.stack: ffff88808a4f8000
RIP: 0010:lbmIODone.cold+0x24/0x5b fs/jfs/jfs_logmgr.c:2325
RSP: 0000:ffff88808a4ffb00 EFLAGS: 00010082
RAX: 000000000000003f RBX: ffff88804e3bac00 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff86ac12c0 RDI: ffffed101149ff56
RBP: 0000000000000020 R08: 000000000000003f R09: 0000000000000001
R10: 0000000000000000 R11: ffff8880603f03c0 R12: 0000000000000286
R13: 0000000000000000 R14: ffff8880a8b6c4c0 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff8880aeb00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f05360f6db8 CR3: 000000008930e000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
bio_endio+0x27a/0x680 block/bio.c:1918
req_bio_endio block/blk-core.c:204 [inline]
blk_update_request+0x2d0/0xa30 block/blk-core.c:2765
blk_mq_end_request+0x4c/0x1e0 block/blk-mq.c:530
__blk_mq_complete_request+0x30b/0x6c0 block/blk-mq.c:571
blk_mq_complete_request+0x52/0x60 block/blk-mq.c:591
loop_handle_cmd drivers/block/loop.c:1784 [inline]
loop_queue_work+0x227/0x1e80 drivers/block/loop.c:1793
kthread_worker_fn+0x271/0x6c0 kernel/kthread.c:642
kthread+0x30d/0x420 kernel/kthread.c:232
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:404
Code: 55 ff e8 cb ff ff ff e8 bd 65 2b ff 48 c7 c1 80 58 d1 86 ba 15 09 00 00 48 c7 c6 00 58 d1 86 48 c7 c7 40 58 d1 86 e8 ff 04 1a ff <0f> 0b e8 97 65 2b ff 48 c7 c1 c0 58 d1 86 ba 16 09 00 00 48 c7
RIP: lbmIODone.cold+0x24/0x5b fs/jfs/jfs_logmgr.c:2325 RSP: ffff88808a4ffb00
---[ end trace 3a4cabc0eca5d418 ]---


---
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.

[syzbot]

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