syzbot


kernel BUG in lbmIODone

Status: auto-obsoleted due to no activity on 2023/08/23 09:03
Reported-by: syzbot+a02ab4f5d800dfa67163@syzkaller.appspotmail.com
First crash: 348d, last: 348d
Similar bugs (8)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream kernel BUG at fs/jfs/jfs_logmgr.c:LINE! jfs 5 1131d 1251d 0/26 auto-closed as invalid on 2021/07/18 05:20
linux-4.14 kernel BUG at fs/jfs/jfs_logmgr.c:LINE! 17 1097d 1310d 0/1 auto-closed as invalid on 2021/08/21 07:16
linux-6.1 kernel BUG in lbmIODone 1 258d 258d 0/3 auto-obsoleted due to no activity on 2023/11/18 07:18
linux-6.1 kernel BUG in lbmIODone (2) 1 27d 27d 0/3 upstream: reported on 2024/03/28 10:22
linux-5.15 kernel BUG in lbmIODone (2) 1 170d 170d 0/3 auto-obsoleted due to no activity on 2024/02/15 02:05
linux-4.14 kernel BUG in lbmIODone jfs syz 13 428d 831d 0/1 upstream: reported syz repro on 2022/01/15 01:14
linux-4.19 kernel BUG at fs/jfs/jfs_logmgr.c:LINE! jfs syz 130 423d 1260d 0/1 upstream: reported syz repro on 2020/11/11 09:07
upstream kernel BUG in lbmIODone jfs C error 99 1d12h 860d 0/26 upstream: reported C repro on 2021/12/16 12:31

Sample crash report:
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: 14 Comm: ksoftirqd/0 Not tainted 5.15.111-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/28/2023
RIP: 0010:lbmIODone+0x16f4/0x1750 fs/jfs/jfs_logmgr.c:2313
Code: 9b 09 36 07 0f 0b e8 bb ba 9c fe 48 c7 c7 c0 d2 c0 8a 48 c7 c6 c0 cd c0 8a ba 09 09 00 00 48 c7 c1 20 dc c0 8a e8 75 09 36 07 <0f> 0b e8 95 ba 9c fe 48 c7 c7 c0 d2 c0 8a 48 c7 c6 c0 cd c0 8a ba
RSP: 0018:ffffc90000d37b00 EFLAGS: 00010046
RAX: 000000000000003f RBX: 0000000000000020 RCX: de78acef8cba9c00
RDX: 0000000080000101 RSI: 0000000080000101 RDI: 0000000000000000
RBP: ffff888033982508 R08: ffffffff8166341c R09: ffffed10173467a0
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffff888033982500 R14: ffff888016bc4278 R15: 0000000000000246
FS:  0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2f421000 CR3: 0000000077ca7000 CR4: 00000000003506f0
Call Trace:
 <TASK>
 req_bio_endio block/blk-core.c:261 [inline]
 blk_update_request+0x87c/0x1470 block/blk-core.c:1447
 blk_mq_end_request+0x3a/0x70 block/blk-mq.c:575
 blk_complete_reqs block/blk-mq.c:587 [inline]
 blk_done_softirq+0xf2/0x130 block/blk-mq.c:592
 __do_softirq+0x3b3/0x93a kernel/softirq.c:558
 run_ksoftirqd+0xc1/0x120 kernel/softirq.c:920
 smpboot_thread_fn+0x51b/0x9d0 kernel/smpboot.c:164
 kthread+0x3f6/0x4f0 kernel/kthread.c:319
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
 </TASK>
Modules linked in:
---[ end trace 1811310ced1eac69 ]---
RIP: 0010:lbmIODone+0x16f4/0x1750 fs/jfs/jfs_logmgr.c:2313
Code: 9b 09 36 07 0f 0b e8 bb ba 9c fe 48 c7 c7 c0 d2 c0 8a 48 c7 c6 c0 cd c0 8a ba 09 09 00 00 48 c7 c1 20 dc c0 8a e8 75 09 36 07 <0f> 0b e8 95 ba 9c fe 48 c7 c7 c0 d2 c0 8a 48 c7 c6 c0 cd c0 8a ba
RSP: 0018:ffffc90000d37b00 EFLAGS: 00010046
RAX: 000000000000003f RBX: 0000000000000020 RCX: de78acef8cba9c00
RDX: 0000000080000101 RSI: 0000000080000101 RDI: 0000000000000000
RBP: ffff888033982508 R08: ffffffff8166341c R09: ffffed10173467a0
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffff888033982500 R14: ffff888016bc4278 R15: 0000000000000246
FS:  0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2f421000 CR3: 0000000077ca7000 CR4: 00000000003506f0

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/05/12 17:08 linux-5.15.y b0ece631f84a ecca8a24 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan kernel BUG in lbmIODone
* Struck through repros no longer work on HEAD.