syzbot


WARNING in nilfs_segctor_do_construct

Status: upstream: reported on 2022/09/28 02:14
Reported-by: syzbot+fbb3e0b24e8dae5a16ee@syzkaller.appspotmail.com
Fix commit: 723ac751208f nilfs2: replace WARN_ONs by nilfs_error for checkpoint acquisition failure
Patched on: [ci-qemu-upstream ci-qemu-upstream-386 ci-qemu2-arm32 ci-qemu2-arm64 ci-qemu2-arm64-compat ci-qemu2-arm64-mte ci-upstream-bpf-kasan-gce ci-upstream-bpf-next-kasan-gce ci-upstream-gce-arm64 ci-upstream-gce-leak ci-upstream-kasan-gce ci-upstream-kasan-gce-386 ci-upstream-kasan-gce-root ci-upstream-kasan-gce-selinux-root ci-upstream-kasan-gce-smack-root ci-upstream-kmsan-gce ci-upstream-kmsan-gce-386 ci-upstream-linux-next-kasan-gce-root ci-upstream-net-kasan-gce ci-upstream-net-this-kasan-gce ci2-upstream-fs ci2-upstream-kcsan-gce ci2-upstream-usb], missing on: [ci-qemu2-riscv64]
First crash: 72d, last: 39d

Sample crash report:
------------[ cut here ]------------
WARNING: CPU: 0 PID: 31729 at fs/nilfs2/segment.c:1482 nilfs_segctor_collect fs/nilfs2/segment.c:1534 [inline]
WARNING: CPU: 0 PID: 31729 at fs/nilfs2/segment.c:1482 nilfs_segctor_do_construct+0x333c/0x6f80 fs/nilfs2/segment.c:2045
Modules linked in:
CPU: 0 PID: 31729 Comm: segctord Not tainted 6.1.0-rc2-syzkaller-00070-g4dc12f37a8e9 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/11/2022
RIP: 0010:nilfs_segctor_truncate_segments fs/nilfs2/segment.c:1482 [inline]
RIP: 0010:nilfs_segctor_collect fs/nilfs2/segment.c:1534 [inline]
RIP: 0010:nilfs_segctor_do_construct+0x333c/0x6f80 fs/nilfs2/segment.c:2045
Code: ff df 80 3c 08 00 74 08 4c 89 ef e8 ee 34 8d fe 4d 8b 6d 00 4c 39 6c 24 58 74 33 e8 3e 3c 39 fe e9 39 ff ff ff e8 34 3c 39 fe <0f> 0b eb c3 44 89 e1 80 e1 07 80 c1 03 38 c1 0f 8c 44 ff ff ff 4c
RSP: 0018:ffffc9000389f6c0 EFLAGS: 00010293
RAX: ffffffff834e93ac RBX: 00000000fffffffe RCX: ffff888074450000
RDX: 0000000000000000 RSI: 00000000fffffffe RDI: 0000000000000000
RBP: ffffc9000389fbf0 R08: ffffffff834e936a R09: ffffed100fb13f01
R10: ffffed100fb13f01 R11: 1ffff1100fb13f00 R12: 0000000000000010
R13: ffff888070f9f768 R14: ffff88808f219af8 R15: dffffc0000000000
FS:  0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f5c7a2a6718 CR3: 00000000361a6000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 nilfs_segctor_construct+0x143/0x8d0 fs/nilfs2/segment.c:2379
 nilfs_segctor_thread_construct fs/nilfs2/segment.c:2487 [inline]
 nilfs_segctor_thread+0x59e/0x11c0 fs/nilfs2/segment.c:2570
 kthread+0x266/0x300 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
 </TASK>

Crashes (3):
Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Title
ci2-upstream-fs 2022/10/27 04:04 upstream 4dc12f37a8e9 86777b7f .config log report info WARNING in nilfs_segctor_do_construct
ci-qemu-upstream 2022/10/24 08:16 upstream 247f34f7b803 faae2fda .config log report info WARNING in nilfs_segctor_do_construct
ci-upstream-linux-next-kasan-gce-root 2022/09/24 02:03 linux-next aaa11ce2ffc8 0042f2b4 .config log report info WARNING in nilfs_segctor_do_construct
* Struck through repros no longer work on HEAD.