[nilfs2?] WARNING in nilfs_segctor_do_construct

4 views
Skip to first unread message

syzbot

unread,
Dec 18, 2022, 10:02:42 AM12/18/22
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: c4215ee4771b Linux 4.14.302
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12e7ad8b880000
kernel config: https://syzkaller.appspot.com/x/.config?x=4a9988fe055c9527
dashboard link: https://syzkaller.appspot.com/bug?extid=e3ebf2fe7ab5700dcaf5
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14bc6217880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1072c7c7880000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c93ba055d204/disk-c4215ee4.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/bfbc929a33c1/vmlinux-c4215ee4.xz
kernel image: https://storage.googleapis.com/syzbot-assets/444658051770/bzImage-c4215ee4.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/0d67cb3c3d0d/mount_0.gz

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

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..


---
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
Reply all
Reply to author
Forward
0 new messages