syzbot


WARNING in nilfs_segctor_abort_construction (2)

Status: upstream: reported on 2025/02/07 07:28
Subsystems: nilfs
[Documentation on labels]
Reported-by: syzbot+86e5da039cef3ad11c6e@syzkaller.appspotmail.com
First crash: 4d12h, last: 4d12h
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [nilfs?] WARNING in nilfs_segctor_abort_construction (2) 0 (1) 2025/02/07 07:28
Similar bugs (1)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream WARNING in nilfs_segctor_abort_construction nilfs 2 106d 114d 0/28 auto-obsoleted due to no activity on 2025/02/01 11:09

Sample crash report:
segctord: attempt to access beyond end of device
loop4: rw=0, sector=80, nr_sectors = 2 limit=0
NILFS (loop4): I/O error reading meta-data file (ino=5, block-offset=0)
------------[ cut here ]------------
WARNING: CPU: 1 PID: 6772 at fs/nilfs2/segment.c:1507 nilfs_cancel_segusage fs/nilfs2/segment.c:1507 [inline]
WARNING: CPU: 1 PID: 6772 at fs/nilfs2/segment.c:1507 nilfs_segctor_abort_construction+0xe51/0xec0 fs/nilfs2/segment.c:1873
Modules linked in:
CPU: 1 UID: 0 PID: 6772 Comm: segctord Not tainted 6.13.0-syzkaller-09760-g69e858e0b8b2 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 12/27/2024
RIP: 0010:nilfs_cancel_segusage fs/nilfs2/segment.c:1507 [inline]
RIP: 0010:nilfs_segctor_abort_construction+0xe51/0xec0 fs/nilfs2/segment.c:1873
Code: 8b 04 25 28 00 00 00 48 3b 84 24 a0 00 00 00 75 74 48 8d 65 d8 5b 41 5c 41 5d 41 5e 41 5f 5d e9 d0 38 6d fd e8 80 64 1c fe 90 <0f> 0b 90 e9 ea f9 ff ff e8 72 64 1c fe 90 0f 0b 90 e9 93 fb ff ff
RSP: 0018:ffffc90003adf5e0 EFLAGS: 00010293
RAX: ffffffff83a30840 RBX: 00000000fffffffb RCX: ffff888025700000
RDX: 0000000000000000 RSI: 00000000fffffffb RDI: 0000000000000000
RBP: ffffc90003adf6d0 R08: ffffffff83a30226 R09: 1ffff1100457f180
R10: dffffc0000000000 R11: ffffed100457f181 R12: 000000000000002f
R13: 0000000000000000 R14: ffff888057ef0008 R15: ffff888055c9a138
FS:  0000000000000000(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f579116b440 CR3: 000000000e738000 CR4: 0000000000350ef0
Call Trace:
 <TASK>
 nilfs_segctor_do_construct+0x6615/0x6ea0 fs/nilfs2/segment.c:2186
 nilfs_segctor_construct+0x181/0x6b0 fs/nilfs2/segment.c:2478
 nilfs_segctor_thread_construct fs/nilfs2/segment.c:2586 [inline]
 nilfs_segctor_thread+0x69e/0xe80 fs/nilfs2/segment.c:2700
 kthread+0x7ab/0x920 kernel/kthread.c:464
 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:148
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
 </TASK>

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/02/03 07:18 upstream 69e858e0b8b2 568559e4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root WARNING in nilfs_segctor_abort_construction
* Struck through repros no longer work on HEAD.