syzbot


kernel BUG in lbmIODone (4)

Status: upstream: reported on 2026/01/16 03:12
Reported-by: syzbot+3fcd00ba75eb8f87da22@syzkaller.appspotmail.com
First crash: 75d, last: 2d08h
Similar bugs (13)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream kernel BUG at fs/jfs/jfs_logmgr.c:LINE! jfs -1 5 1838d 1958d 0/29 auto-closed as invalid on 2021/07/18 05:20
linux-5.15 kernel BUG in lbmIODone -1 1 1055d 1055d 0/3 auto-obsoleted due to no activity on 2023/08/23 09:03
linux-4.14 kernel BUG at fs/jfs/jfs_logmgr.c:LINE! -1 17 1804d 2017d 0/1 auto-closed as invalid on 2021/08/21 07:16
linux-6.1 kernel BUG in lbmIODone -1 1 965d 965d 0/3 auto-obsoleted due to no activity on 2023/11/18 07:18
linux-6.1 kernel BUG in lbmIODone (2) -1 1 734d 734d 0/3 auto-obsoleted due to no activity on 2024/07/06 10:22
linux-5.15 kernel BUG in lbmIODone (2) -1 1 876d 876d 0/3 auto-obsoleted due to no activity on 2024/02/15 02:05
linux-4.14 kernel BUG in lbmIODone jfs -1 syz 13 1135d 1537d 0/1 upstream: reported syz repro on 2022/01/15 01:14
upstream kernel BUG in lbmIODone (2) jfs -1 1 418d 414d 0/29 auto-obsoleted due to no activity on 2025/05/18 00:22
linux-6.1 kernel BUG in lbmIODone (3) -1 3 329d 445d 0/3 auto-obsoleted due to no activity on 2025/08/14 20:20
linux-4.19 kernel BUG at fs/jfs/jfs_logmgr.c:LINE! jfs -1 syz 130 1130d 1967d 0/1 upstream: reported syz repro on 2020/11/11 09:07
linux-5.15 kernel BUG in lbmIODone (3) -1 1 705d 705d 0/3 auto-obsoleted due to no activity on 2024/08/04 15:04
upstream kernel BUG in lbmIODone jfs -1 C error error 135 606d 1567d 0/29 auto-obsoleted due to no activity on 2024/11/10 13:25
upstream kernel BUG in lbmIODone (3) jfs -1 4 143d 201d 0/29 auto-obsoleted due to no activity on 2026/02/17 01:16

Sample crash report:
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 syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2026
RIP: 0010:lbmIODone+0x1622/0x1670 fs/jfs/jfs_logmgr.c:2298
Code: 74 ca 2e 07 0f 0b e8 4d b1 8e fe 48 c7 c7 e0 36 c6 8a 48 c7 c6 e0 31 c6 8a ba fa 08 00 00 48 c7 c1 60 40 c6 8a e8 4e ca 2e 07 <0f> 0b e8 27 b1 8e fe 48 c7 c7 e0 36 c6 8a 48 c7 c6 e0 31 c6 8a ba
RSP: 0018:ffffc90000147ab8 EFLAGS: 00010046
RAX: 000000000000003f RBX: 0000000000000020 RCX: 8e55bdd4a8859a00
RDX: 0000000000000100 RSI: 0000000080000101 RDI: 0000000000000000
RBP: ffff888145bae308 R08: ffffc900001477c7 R09: 1ffff92000028ef8
R10: dffffc0000000000 R11: fffff52000028ef9 R12: ffff888145bae300
R13: dffffc0000000000 R14: 0000000000000a06 R15: ffff888027576a78
FS:  0000000000000000(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f6b88d46000 CR3: 000000007b7d3000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 req_bio_endio block/blk-mq.c:782 [inline]
 blk_update_request+0x593/0xe30 block/blk-mq.c:927
 blk_mq_end_request+0x3a/0x70 block/blk-mq.c:1052
 blk_complete_reqs block/blk-mq.c:1132 [inline]
 blk_done_softirq+0x100/0x150 block/blk-mq.c:1137
 handle_softirqs+0x2a1/0x930 kernel/softirq.c:596
 run_ksoftirqd+0xa4/0x100 kernel/softirq.c:968
 smpboot_thread_fn+0x64a/0xa40 kernel/smpboot.c:164
 kthread+0x29d/0x330 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:lbmIODone+0x1622/0x1670 fs/jfs/jfs_logmgr.c:2298
Code: 74 ca 2e 07 0f 0b e8 4d b1 8e fe 48 c7 c7 e0 36 c6 8a 48 c7 c6 e0 31 c6 8a ba fa 08 00 00 48 c7 c1 60 40 c6 8a e8 4e ca 2e 07 <0f> 0b e8 27 b1 8e fe 48 c7 c7 e0 36 c6 8a 48 c7 c6 e0 31 c6 8a ba
RSP: 0018:ffffc90000147ab8 EFLAGS: 00010046
RAX: 000000000000003f RBX: 0000000000000020 RCX: 8e55bdd4a8859a00
RDX: 0000000000000100 RSI: 0000000080000101 RDI: 0000000000000000
RBP: ffff888145bae308 R08: ffffc900001477c7 R09: 1ffff92000028ef8
R10: dffffc0000000000 R11: fffff52000028ef9 R12: ffff888145bae300
R13: dffffc0000000000 R14: 0000000000000a06 R15: ffff888027576a78
FS:  0000000000000000(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f6b88d46000 CR3: 000000007b7d3000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400

Crashes (3):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/03/30 10:39 linux-6.1.y 1989cd3d56e2 dcaebc52 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan kernel BUG in lbmIODone
2026/03/24 03:07 linux-6.1.y f2ddafa93a25 baf8bf12 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan kernel BUG in lbmIODone
2026/01/16 03:10 linux-6.1.y bec0e10ee67e d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan kernel BUG in lbmIODone
* Struck through repros no longer work on HEAD.