syzbot


kernel BUG in lbmIODone

Status: upstream: reported syz repro on 2022/01/15 01:14
Subsystems: jfs
[Documentation on labels]
Reported-by: syzbot+cb8224131116f1986389@syzkaller.appspotmail.com
First crash: 831d, last: 428d
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 1132d 1251d 0/26 auto-closed as invalid on 2021/07/18 05:20
linux-5.15 kernel BUG in lbmIODone 1 348d 348d 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! 17 1098d 1310d 0/1 auto-closed as invalid on 2021/08/21 07:16
linux-6.1 kernel BUG in lbmIODone 1 259d 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.19 kernel BUG at fs/jfs/jfs_logmgr.c:LINE! jfs syz 130 424d 1260d 0/1 upstream: reported syz repro on 2020/11/11 09:07
upstream kernel BUG in lbmIODone jfs C error 99 1d16h 860d 0/26 upstream: reported C repro on 2021/12/16 12:31
Fix bisection attempts (1)
Created Duration User Patch Repo Result
2023/02/17 00:42 30m bisect fix linux-4.14.y job log (0) log

Sample crash report:
BUG at fs/jfs/jfs_logmgr.c:2326 assert(bp->l_flag & lbmRELEASE)
------------[ cut here ]------------
kernel BUG at fs/jfs/jfs_logmgr.c:2326!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
Modules linked in:
CPU: 1 PID: 19702 Comm: loop2 Not tainted 4.14.295-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022
task: ffff8880981901c0 task.stack: ffff888091c10000
RIP: 0010:lbmIODone.cold+0x24/0x5b fs/jfs/jfs_logmgr.c:2326
RSP: 0000:ffff888091c17b00 EFLAGS: 00010082
RAX: 000000000000003f RBX: ffff8880a0020300 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff878bc9e0 RDI: ffffed1012382f56
RBP: 0000000000000020 R08: 000000000000003f R09: 0000000000000001
R10: 0000000000000000 R11: ffff8880981901c0 R12: 0000000000000286
R13: 0000000000000000 R14: ffff8880a8c204c0 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffff8880ba500000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fdbd0f5e1b8 CR3: 00000000aa15c000 CR4: 00000000003406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 bio_endio+0x290/0x690 block/bio.c:1918
 req_bio_endio block/blk-core.c:204 [inline]
 blk_update_request+0x2d0/0xa90 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:1789 [inline]
 loop_queue_work+0x228/0x21e0 drivers/block/loop.c:1798
 kthread_worker_fn+0x271/0x6c0 kernel/kthread.c:667
 kthread+0x30d/0x420 kernel/kthread.c:232
 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:404
Code: 76 fa e8 cb ff ff ff e8 78 30 4d fa 48 c7 c1 00 ba b6 87 ba 16 09 00 00 48 c7 c6 80 b9 b6 87 48 c7 c7 c0 b9 b6 87 e8 de b9 fa ff <0f> 0b e8 52 30 4d fa 48 c7 c1 40 ba b6 87 ba 17 09 00 00 48 c7 
RIP: lbmIODone.cold+0x24/0x5b fs/jfs/jfs_logmgr.c:2326 RSP: ffff888091c17b00
---[ end trace 600443062d4c1d30 ]---

Crashes (13):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2022/10/09 01:30 linux-4.14.y 9d5c0b3a8e1a aea5da89 .config console log report syz [disk image] [vmlinux] [mounted in repro] ci2-linux-4-14 kernel BUG in lbmIODone
2022/09/28 18:52 linux-4.14.y 9d5c0b3a8e1a 75c78242 .config console log report syz [disk image] [vmlinux] ci2-linux-4-14 kernel BUG in lbmIODone
2023/02/21 08:16 linux-4.14.y a8ad60f2af58 f949448d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 kernel BUG in lbmIODone
2023/01/17 23:54 linux-4.14.y c4215ee4771b 42660d9e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 kernel BUG in lbmIODone
2023/01/12 03:00 linux-4.14.y c4215ee4771b 96166539 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 kernel BUG in lbmIODone
2023/01/04 19:24 linux-4.14.y c4215ee4771b 1dac8c7a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 kernel BUG in lbmIODone
2022/12/06 20:18 linux-4.14.y 179ef7fe8677 d88f3abb .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 kernel BUG in lbmIODone
2022/10/26 13:40 linux-4.14.y 41f36d7859a7 2159e4d2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 kernel BUG in lbmIODone
2022/10/21 09:29 linux-4.14.y 9d5c0b3a8e1a 63e790dd .config console log report info [disk image] [vmlinux] ci2-linux-4-14 kernel BUG in lbmIODone
2022/06/20 15:17 linux-4.14.y 84bae26850e3 b9406563 .config console log report info ci2-linux-4-14 kernel BUG in lbmIODone
2022/05/20 18:07 linux-4.14.y dffb5c6ff09c bd37ad7e .config console log report info ci2-linux-4-14 kernel BUG in lbmIODone
2022/03/31 13:07 linux-4.14.y af1af6ebca0e c4c32d8c .config console log report info ci2-linux-4-14 kernel BUG in lbmIODone
2022/01/15 01:13 linux-4.14.y 4ba8e26127c3 53e00b45 .config console log report info ci2-linux-4-14 kernel BUG in lbmIODone
* Struck through repros no longer work on HEAD.