syzbot

 sign-in | mailing list | source | docs
🐞 Open [1606]
≡ Subsystems
🐞 Fixed [5937]
🐞 Invalid [14469]
⬇ Missing Backports [106]
≡ Crashes
Kernel Health Bugs/Month Bug Lifetimes Fuzzing
Total Repo Heatmap Subsystems Heatmap
💬 Send us feedback

kernel BUG in folio_end_writeback

Status: auto-obsoleted due to no activity on 2024/03/16 05:37
Subsystems: nilfs
[Documentation on labels]
Reported-by: syzbot+7e5cf1d80677ec185e63@syzkaller.appspotmail.com
First crash: 734d, last: 385d
Cause bisection: failed (error log, bisect log)
  
Fix bisection: fixed by (bisect log) :
commit 92c5d1b860e9581d64baca76779576c0ab0d943d
Author: Ryusuke Konishi <konishi.ryusuke@gmail.com>
Date: Fri May 26 02:13:32 2023 +0000

  nilfs2: reject devices with insufficient block count

  
▶ ▼ Discussions (6)
Title Replies (including bot) Last reply
[syzbot] Monthly nilfs report (Dec 2023) 0 (1) 2023/12/02 14:45
[syzbot] [nilfs2?] kernel BUG in folio_end_writeback 1 (3) 2023/08/21 16:47
[syzbot] Monthly nilfs report (Jun 2023) 0 (1) 2023/06/29 08:55
[syzbot] Monthly nilfs report (May 2023) 0 (1) 2023/05/29 08:50
[syzbot] Monthly nilfs report (Apr 2023) 0 (1) 2023/04/27 10:39
[syzbot] Monthly mm report 3 (4) 2023/04/06 10:02
▶ ▼ Similar bugs (1)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.1 kernel BUG in folio_end_writeback origin:upstream C unreliable 1 394d 598d 0/3 auto-obsoleted due to no activity on 2024/03/07 11:15
▶ ▼ Last patch testing requests (10)
Created Duration User Patch Repo Result
2024/02/17 02:28 20m retest repro upstream OK log
2024/02/15 10:59 36m retest repro upstream OK log
2024/01/27 23:26 21m retest repro upstream OK log
2024/01/27 23:26 19m retest repro upstream OK log
2024/01/14 01:45 23m retest repro linux-next OK log
2023/12/07 04:46 25m retest repro upstream report log
2023/12/07 04:46 24m retest repro upstream report log
2023/11/18 21:25 12m retest repro upstream report log
2023/11/18 21:25 11m retest repro upstream report log
2023/11/04 18:33 15m retest repro linux-next report log

Sample crash report:
NILFS (loop4): segctord starting. Construction interval = 5 seconds, CP frequency < 30 seconds
------------[ cut here ]------------
kernel BUG at mm/filemap.c:1619!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 5357 Comm: segctord Not tainted 6.3.0-rc2-syzkaller-00077-g38e04b3e4240 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
RIP: 0010:folio_end_writeback+0x43a/0x700 mm/filemap.c:1619
Code: 84 db 00 00 00 e8 f6 32 d1 ff e9 48 fc ff ff e8 ec 32 d1 ff 4c 89 ff 48 c7 c6 a0 ab f2 8a e8 4d a7 0f 00 0f 0b e8 d6 32 d1 ff <0f> 0b e8 cf 32 d1 ff 4c 89 ff 48 c7 c6 60 ae f2 8a e8 30 a7 0f 00
RSP: 0018:ffffc900045bf6b8 EFLAGS: 00010293
RAX: ffffffff81b93a4a RBX: 0000000000000082 RCX: ffff8880280d9d40
RDX: 0000000000000000 RSI: ffffffff8aea8ee0 RDI: ffffffff8b3801c0
RBP: 0000000000000000 R08: dffffc0000000000 R09: fffffbfff1ca6e46
R10: 0000000000000000 R11: dffffc0000000001 R12: ffffea0001f8c8b4
R13: 1ffffd40003f1916 R14: ffffea0001f8c888 R15: ffffea0001f8c880
FS:  0000000000000000(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f3437229000 CR3: 00000000293cd000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 nilfs_segctor_complete_write fs/nilfs2/segment.c:1870 [inline]
 nilfs_segctor_wait fs/nilfs2/segment.c:1931 [inline]
 nilfs_segctor_do_construct+0x5544/0x6f70 fs/nilfs2/segment.c:2094
 nilfs_segctor_construct+0x145/0x8c0 fs/nilfs2/segment.c:2381
 nilfs_segctor_thread_construct fs/nilfs2/segment.c:2489 [inline]
 nilfs_segctor_thread+0x53a/0x1140 fs/nilfs2/segment.c:2572
 kthread+0x270/0x300 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:folio_end_writeback+0x43a/0x700 mm/filemap.c:1619
Code: 84 db 00 00 00 e8 f6 32 d1 ff e9 48 fc ff ff e8 ec 32 d1 ff 4c 89 ff 48 c7 c6 a0 ab f2 8a e8 4d a7 0f 00 0f 0b e8 d6 32 d1 ff <0f> 0b e8 cf 32 d1 ff 4c 89 ff 48 c7 c6 60 ae f2 8a e8 30 a7 0f 00
RSP: 0018:ffffc900045bf6b8 EFLAGS: 00010293
RAX: ffffffff81b93a4a RBX: 0000000000000082 RCX: ffff8880280d9d40
RDX: 0000000000000000 RSI: ffffffff8aea8ee0 RDI: ffffffff8b3801c0
RBP: 0000000000000000 R08: dffffc0000000000 R09: fffffbfff1ca6e46
R10: 0000000000000000 R11: dffffc0000000001 R12: ffffea0001f8c8b4
R13: 1ffffd40003f1916 R14: ffffea0001f8c888 R15: ffffea0001f8c880
FS:  0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fff08ad0e58 CR3: 0000000029f0f000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400

Crashes (41):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/03/17 23:06 upstream 38e04b3e4240 7939252e .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs kernel BUG in folio_end_writeback
2023/02/03 01:20 upstream 9f266ccaa2f5 16d19e30 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-root kernel BUG in folio_end_writeback
2022/12/23 04:02 upstream 0a924817d2ed 9da18ae8 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs kernel BUG in folio_end_writeback
2023/06/01 21:30 upstream 929ed21dfdb6 a4ae4f42 .config console log report syz C [mounted in repro] ci-upstream-kasan-gce-root kernel BUG in folio_end_writeback
2023/05/28 08:19 upstream 4e893b5aa4ac cf184559 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-root kernel BUG in folio_end_writeback
2023/07/07 17:10 linux-next 123212f53f3e 22ae5830 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-linux-next-kasan-gce-root kernel BUG in folio_end_writeback
2023/11/23 04:24 upstream 9b6de136b5f0 03e12510 .config console log report syz [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-selinux-root kernel BUG in folio_end_writeback
2023/06/28 01:03 upstream b19edac5992d 4cd5bb25 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs kernel BUG in folio_end_writeback
2023/06/25 16:12 upstream a92b7d26c743 79782afc .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs kernel BUG in folio_end_writeback
2023/06/20 23:01 upstream 99ec1ed7c2ed 79782afc .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs kernel BUG in folio_end_writeback
2023/06/13 02:14 upstream fd37b884003c aaed0183 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs kernel BUG in folio_end_writeback
2023/06/08 05:57 upstream a27648c74210 058b3a5a .config console log report info ci2-upstream-fs kernel BUG in folio_end_writeback
2023/06/06 18:38 upstream a4d7d7011219 a4ae4f42 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs kernel BUG in folio_end_writeback
2023/05/30 10:22 upstream 8b817fded42d cf184559 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs kernel BUG in folio_end_writeback
2023/05/24 16:41 upstream 9d646009f65d 4bce1a3e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs kernel BUG in folio_end_writeback
2023/05/11 05:41 upstream d295b66a7b66 0fbd49f4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs kernel BUG in folio_end_writeback
2023/04/18 19:51 upstream af67688dca57 d931e9f0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs kernel BUG in folio_end_writeback
2023/04/16 03:27 upstream a7a55e27ad72 ec410564 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs kernel BUG in folio_end_writeback
2023/04/14 05:25 upstream 44149752e998 3cfcaa1b .config console log report info ci-qemu-upstream kernel BUG in folio_end_writeback
2023/04/10 14:18 upstream 09a9639e56c0 71147e29 .config console log report info ci2-upstream-fs kernel BUG in folio_end_writeback
2023/04/10 06:33 upstream 09a9639e56c0 71147e29 .config console log report info ci-qemu-upstream kernel BUG in folio_end_writeback
2023/04/09 17:25 upstream cdc9718d5e59 71147e29 .config console log report info ci2-upstream-fs kernel BUG in folio_end_writeback
2023/04/08 02:19 upstream aa318c48808c 71147e29 .config console log report info ci-qemu-upstream kernel BUG in folio_end_writeback
2023/04/07 15:09 upstream f2afccfefe7b f7ba566d .config console log report info ci-qemu-upstream kernel BUG in folio_end_writeback
2023/04/06 13:45 upstream 99ddf2254feb 08707520 .config console log report info ci-qemu-upstream kernel BUG in folio_end_writeback
2023/03/30 20:27 upstream 8bb95a1662f8 f325deb0 .config console log report info ci-qemu-upstream kernel BUG in folio_end_writeback
2023/03/30 08:44 upstream ffe78bbd5121 f325deb0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs kernel BUG in folio_end_writeback
2023/03/24 13:25 upstream 1e760fa3596e f94b4a29 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs kernel BUG in folio_end_writeback
2023/03/20 05:41 upstream e8d018dd0257 7939252e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs kernel BUG in folio_end_writeback
2023/03/19 09:34 upstream 534293368afa 7939252e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs kernel BUG in folio_end_writeback
2023/03/17 01:43 upstream 0ddc84d2dd43 18b58603 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs kernel BUG in folio_end_writeback
2023/03/15 13:28 upstream 6015b1aca1a2 18b58603 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs kernel BUG in folio_end_writeback
2023/03/15 09:45 upstream 6015b1aca1a2 18b58603 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs kernel BUG in folio_end_writeback
2023/03/12 19:47 upstream 134231664868 5205ef30 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs kernel BUG in folio_end_writeback
2023/02/27 15:15 upstream f3a2439f20d9 9189cb53 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs kernel BUG in folio_end_writeback
2023/02/25 17:09 upstream 489fa31ea873 ee50e71c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs kernel BUG in folio_end_writeback
2023/02/24 19:58 upstream d2980d8d8265 ee50e71c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs kernel BUG in folio_end_writeback
2023/02/13 11:59 upstream ceaa837f96ad 957959cb .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs kernel BUG in folio_end_writeback
2023/01/06 03:25 upstream 41c03ba9beea 1dac8c7a .config console log report info ci2-upstream-fs kernel BUG in folio_end_writeback
2022/12/23 03:32 upstream 0a924817d2ed 9da18ae8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs kernel BUG in folio_end_writeback
2023/04/10 04:08 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 9a03cbd79d3a 71147e29 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 kernel BUG in folio_end_writeback
* Struck through repros no longer work on HEAD.