WARNING in nilfs_segctor_do_construct

Status: upstream: reported C repro on 2022/12/18 15:02
Subsystems: nilfs2
[Documentation on labels]
Reported-by: syzbot+e3ebf2fe7ab5700dcaf5@syzkaller.appspotmail.com
First crash: 1315d, last: 1240d
▶ ▼ Similar bugs (5)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-5.15 WARNING in nilfs_segctor_do_construct -1 C done 2 1142d 1164d 3/3 fixed on 2023/07/20 13:49
linux-6.6 WARNING in nilfs_segctor_do_construct origin:lts-only -1 C 121 17d 92d 0/2 upstream: reported C repro on 2026/04/24 08:03
upstream WARNING in nilfs_segctor_do_construct (2) nilfs -1 C error 3 1169d 1167d 23/29 fixed on 2023/07/04 09:17
linux-6.1 WARNING in nilfs_segctor_do_construct -1 C done 2 1139d 1168d 3/3 fixed on 2023/07/26 10:02
upstream WARNING in nilfs_segctor_do_construct nilfs -1 C 5 1273d 1396d 22/29 fixed on 2023/02/24 13:50
▶ ▼ Fix bisection attempts (2)
Created Duration User Patch Repo Result
2023/03/02 21:15 26m bisect fix linux-4.14.y OK (0) job log log
2023/01/31 05:14 22m bisect fix linux-4.14.y OK (0) job log log

Sample crash report:
IPv6: ADDRCONF(NETDEV_CHANGE): veth1_to_batadv: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
NILFS (loop0): segctord starting. Construction interval = 5 seconds, CP frequency < 30 seconds
NILFS (loop0): nilfs_sufile_update: invalid segment number: 53
------------[ cut here ]------------
WARNING: CPU: 0 PID: 8230 at fs/nilfs2/segment.c:1495 nilfs_segctor_truncate_segments fs/nilfs2/segment.c:1495 [inline]
WARNING: CPU: 0 PID: 8230 at fs/nilfs2/segment.c:1495 nilfs_segctor_collect fs/nilfs2/segment.c:1547 [inline]
WARNING: CPU: 0 PID: 8230 at fs/nilfs2/segment.c:1495 nilfs_segctor_do_construct+0x464d/0x79c0 fs/nilfs2/segment.c:2058
Kernel panic - not syncing: panic_on_warn set ...

CPU: 0 PID: 8230 Comm: segctord Not tainted 4.14.302-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
Call Trace:
 __dump_stack lib/dump_stack.c:17 [inline]
 dump_stack+0x1b2/0x281 lib/dump_stack.c:58
 panic+0x1f9/0x42d kernel/panic.c:183
 __warn.cold+0x20/0x44 kernel/panic.c:547
 report_bug+0x208/0x250 lib/bug.c:183
 fixup_bug arch/x86/kernel/traps.c:177 [inline]
 fixup_bug arch/x86/kernel/traps.c:172 [inline]
 do_error_trap+0x195/0x2d0 arch/x86/kernel/traps.c:295
 invalid_op+0x1b/0x40 arch/x86/entry/entry_64.S:967
RIP: 0010:nilfs_segctor_truncate_segments fs/nilfs2/segment.c:1495 [inline]
RIP: 0010:nilfs_segctor_collect fs/nilfs2/segment.c:1547 [inline]
RIP: 0010:nilfs_segctor_do_construct+0x464d/0x79c0 fs/nilfs2/segment.c:2058
RSP: 0018:ffff8880b01cfb98 EFLAGS: 00010297
RAX: ffff8880b3374240 RBX: ffff8880950bdbf0 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff878bd020 RDI: ffffed1016039f52
RBP: ffff88808dfeb6f8 R08: 000000000000003e R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: ffff88808dfb7200
R13: ffffed1012a17b82 R14: dffffc0000000000 R15: ffff8880950bdb40
 nilfs_segctor_construct+0x6db/0x8e0 fs/nilfs2/segment.c:2394
 nilfs_segctor_thread_construct fs/nilfs2/segment.c:2502 [inline]
 nilfs_segctor_thread+0x3ad/0xdb0 fs/nilfs2/segment.c:2586
 kthread+0x30d/0x420 kernel/kthread.c:232
 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:406
Kernel Offset: disabled
Rebooting in 86400 seconds..

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2022/12/18 15:02 linux-4.14.y c4215ee4771b 05494336 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-4-14 WARNING in nilfs_segctor_do_construct
* Struck through repros no longer work on HEAD.