[syzbot] [nilfs?] WARNING in nilfs_segctor_abort_construction (3)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 8fde5d1d47f6 Merge tag 'acpi-7.1-rc6' of git://git.kernel...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14bd1ab6580000
kernel config: https://syzkaller.appspot.com/x/.config?x=b4166e8ea5fbf7e3
dashboard link: https://syzkaller.appspot.com/bug?extid=5957361606d7b750b874
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-8fde5d1d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/9d8eca02a966/vmlinux-8fde5d1d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/01e3e901b0a4/bzImage-8fde5d1d.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+595736...@syzkaller.appspotmail.com

NILFS (loop0): segctord starting. Construction interval = 5 seconds, CP frequency < 30 seconds
NILFS error (device loop0): nilfs_bmap_lookup_at_level: broken bmap (inode number=4)
NILFS error (device loop0): nilfs_bmap_lookup_at_level: broken bmap (inode number=5)
------------[ cut here ]------------
ret
WARNING: fs/nilfs2/segment.c:1507 at nilfs_cancel_segusage fs/nilfs2/segment.c:1507 [inline], CPU#0: segctord/5339
WARNING: fs/nilfs2/segment.c:1507 at nilfs_segctor_abort_construction+0xd7d/0xde0 fs/nilfs2/segment.c:1873, CPU#0: segctord/5339
Modules linked in:
CPU: 0 UID: 0 PID: 5339 Comm: segctord Not tainted syzkaller #0 PREEMPT(full)
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
RIP: 0010:nilfs_cancel_segusage fs/nilfs2/segment.c:1507 [inline]
RIP: 0010:nilfs_segctor_abort_construction+0xd7d/0xde0 fs/nilfs2/segment.c:1873
Code: 8b 05 67 50 84 0f 48 3b 84 24 a0 00 00 00 75 3e 48 8d 65 d8 5b 41 5c 41 5d 41 5e 41 5f 5d e9 8a ca f7 07 cc e8 64 47 11 fe 90 <0f> 0b 90 e9 cc f9 ff ff e8 56 47 11 fe 90 0f 0b 90 e9 60 fb ff ff
RSP: 0018:ffffc900039ef5e0 EFLAGS: 00010293
RAX: ffffffff83b47fdc RBX: ffff88800e4ac2c8 RCX: ffff88801fb1ca80
RDX: 0000000000000000 RSI: 00000000fffffffb RDI: 0000000000000000
RBP: ffffc900039ef6d0 R08: ffff8880436efa07 R09: 1ffff110086ddf40
R10: dffffc0000000000 R11: ffffed10086ddf41 R12: 0000000000000000
R13: ffff88800e4ac338 R14: ffff888046f765b0 R15: 00000000fffffffb
FS: 0000000000000000(0000) GS:ffff88808c893000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fe074a99e3a CR3: 000000000bb60000 CR4: 0000000000352ef0
Call Trace:
<TASK>
nilfs_segctor_do_construct+0x6e3f/0x76c0 fs/nilfs2/segment.c:2186
nilfs_segctor_construct+0x17b/0x690 fs/nilfs2/segment.c:2462
nilfs_segctor_thread_construct fs/nilfs2/segment.c:2570 [inline]
nilfs_segctor_thread+0x6c0/0xdc0 fs/nilfs2/segment.c:2684
kthread+0x389/0x470 kernel/kthread.c:436
ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
</TASK>


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup