WARNING in nilfs_sufile_set_segment_usage

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 7878a41b6cc1 Linux 4.14.307
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10033098c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=77c994a24403ce1c
dashboard link: https://syzkaller.appspot.com/bug?extid=9f644a2fe13c164a4d3a
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17e02eb0c80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=155393a8c80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/1fdebf709d79/disk-7878a41b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/88229e373f4d/vmlinux-7878a41b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/bf3c4c287a8b/bzImage-7878a41b.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/3d5fbfbe3f65/mount_0.gz

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

NILFS (loop0): segctord starting. Construction interval = 5 seconds, CP frequency < 30 seconds
audit: type=1800 audit(1677765458.425:2): pid=7967 uid=0 auid=4294967295 ses=4294967295 op="collect_data" cause="failed(directio)" comm="syz-executor149" name="bus" dev="loop0" ino=18 res=0
------------[ cut here ]------------
WARNING: CPU: 1 PID: 7994 at fs/nilfs2/sufile.c:551 nilfs_sufile_set_segment_usage+0x461/0x5f0 fs/nilfs2/sufile.c:551
Kernel panic - not syncing: kernel: panic_on_warn set ...

CPU: 1 PID: 7994 Comm: segctord Not tainted 4.14.307-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/16/2023
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x1b2/0x281 lib/dump_stack.c:58
panic+0x21d/0x451 kernel/panic.c:247
check_panic_on_warn.cold+0x19/0x35 kernel/panic.c:171
__warn+0xdf/0x1e0 kernel/panic.c:603
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_sufile_set_segment_usage+0x461/0x5f0 fs/nilfs2/sufile.c:551
RSP: 0018:ffff8880b3d57af8 EFLAGS: 00010297
RAX: ffff8880b363e4c0 RBX: ffff88808cf91200 RCX: ffff8880a893d000
RDX: 0000000000000000 RSI: 1ffff11014446f51 RDI: ffff8880a893d06c
RBP: ffff8880a893d060 R08: ffff8880a2237a00 R09: 0000000000000000
R10: 0000000000000000 R11: ffff8880b363e4c0 R12: 0000000000000000
R13: 1ffff110167aaf64 R14: ffff88808cf915b0 R15: 000000006400ab52
nilfs_segctor_update_segusage fs/nilfs2/segment.c:1460 [inline]
nilfs_segctor_do_construct+0x1c82/0x79c0 fs/nilfs2/segment.c:2084
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..


---
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.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches