WARNING in nilfs_dat_commit_end
9 views
Skip to first unread message
syzbot
Sep 30, 2022, 9:59:43 AM9/30/22
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 3f8a27f9e27b Linux 4.19.211
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1717d3ef080000
kernel config: https://syzkaller.appspot.com/x/.config?x=9b9277b418617afe
dashboard link: https://syzkaller.appspot.com/bug?extid=8e7d254e1b66afa8face
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=141c5570880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=158af7df080000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+8e7d25...@syzkaller.appspotmail.com
IPVS: ftp: loaded support on port[0] = 21
NILFS (loop0): broken superblock, retrying with spare superblock (blocksize = 1024)
NILFS (loop0): segctord starting. Construction interval = 5 seconds, CP frequency < 30 seconds
------------[ cut here ]------------
WARNING: CPU: 1 PID: 8126 at fs/nilfs2/dat.c:186 nilfs_dat_commit_end.cold+0x11/0x18 fs/nilfs2/dat.c:186
Kernel panic - not syncing: panic_on_warn set ...
CPU: 1 PID: 8126 Comm: segctord Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1fc/0x2ef lib/dump_stack.c:118
panic+0x26a/0x50e kernel/panic.c:186
__warn.cold+0x20/0x5a kernel/panic.c:541
report_bug+0x262/0x2b0 lib/bug.c:183
fixup_bug arch/x86/kernel/traps.c:178 [inline]
fixup_bug arch/x86/kernel/traps.c:173 [inline]
do_error_trap+0x1d7/0x310 arch/x86/kernel/traps.c:296
invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:1038
RIP: 0010:nilfs_dat_commit_end.cold+0x11/0x18 fs/nilfs2/dat.c:186
Code: fa e8 98 4f 69 f9 48 c7 c7 80 df 9e 88 e8 f7 80 fa ff 0f 0b e9 1a 66 b6 fa e8 80 4f 69 f9 48 c7 c7 80 df 9e 88 e8 df 80 fa ff <0f> 0b e9 0e 69 b6 fa e8 68 4f 69 f9 48 c7 c7 80 df 9e 88 e8 c7 80
RSP: 0018:ffff888095277810 EFLAGS: 00010286
RAX: 0000000000000024 RBX: ffff8880ab8aba40 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff814dff01 RDI: ffffed1012a4eef4
RBP: ffff8880952778b8 R08: 0000000000000024 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: ffff88808e1b19c0
R13: 000023d50af30002 R14: ffff8880952778d0 R15: 0000000000000003
nilfs_dat_commit_update+0x26/0x40 fs/nilfs2/dat.c:236
nilfs_direct_propagate fs/nilfs2/direct.c:277 [inline]
nilfs_direct_propagate+0x237/0x2f0 fs/nilfs2/direct.c:256
nilfs_bmap_propagate+0x73/0x170 fs/nilfs2/bmap.c:337
nilfs_collect_file_data+0x45/0xd0 fs/nilfs2/segment.c:573
nilfs_segctor_apply_buffers+0x14a/0x490 fs/nilfs2/segment.c:1014
nilfs_segctor_scan_file+0x3f4/0x6f0 fs/nilfs2/segment.c:1063
nilfs_segctor_collect_blocks fs/nilfs2/segment.c:1170 [inline]
nilfs_segctor_collect fs/nilfs2/segment.c:1494 [inline]
nilfs_segctor_do_construct+0x242b/0x8360 fs/nilfs2/segment.c:2036
nilfs_segctor_construct+0x764/0xae0 fs/nilfs2/segment.c:2372
nilfs_segctor_thread_construct fs/nilfs2/segment.c:2480 [inline]
nilfs_segctor_thread+0x3cb/0xf50 fs/nilfs2/segment.c:2563
kthread+0x33f/0x460 kernel/kthread.c:259
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415
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
syzbot found the following issue on:
HEAD commit: 3f8a27f9e27b Linux 4.19.211
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1717d3ef080000
kernel config: https://syzkaller.appspot.com/x/.config?x=9b9277b418617afe
dashboard link: https://syzkaller.appspot.com/bug?extid=8e7d254e1b66afa8face
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=141c5570880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=158af7df080000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+8e7d25...@syzkaller.appspotmail.com
IPVS: ftp: loaded support on port[0] = 21
NILFS (loop0): broken superblock, retrying with spare superblock (blocksize = 1024)
NILFS (loop0): segctord starting. Construction interval = 5 seconds, CP frequency < 30 seconds
------------[ cut here ]------------
WARNING: CPU: 1 PID: 8126 at fs/nilfs2/dat.c:186 nilfs_dat_commit_end.cold+0x11/0x18 fs/nilfs2/dat.c:186
Kernel panic - not syncing: panic_on_warn set ...
CPU: 1 PID: 8126 Comm: segctord Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1fc/0x2ef lib/dump_stack.c:118
panic+0x26a/0x50e kernel/panic.c:186
__warn.cold+0x20/0x5a kernel/panic.c:541
report_bug+0x262/0x2b0 lib/bug.c:183
fixup_bug arch/x86/kernel/traps.c:178 [inline]
fixup_bug arch/x86/kernel/traps.c:173 [inline]
do_error_trap+0x1d7/0x310 arch/x86/kernel/traps.c:296
invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:1038
RIP: 0010:nilfs_dat_commit_end.cold+0x11/0x18 fs/nilfs2/dat.c:186
Code: fa e8 98 4f 69 f9 48 c7 c7 80 df 9e 88 e8 f7 80 fa ff 0f 0b e9 1a 66 b6 fa e8 80 4f 69 f9 48 c7 c7 80 df 9e 88 e8 df 80 fa ff <0f> 0b e9 0e 69 b6 fa e8 68 4f 69 f9 48 c7 c7 80 df 9e 88 e8 c7 80
RSP: 0018:ffff888095277810 EFLAGS: 00010286
RAX: 0000000000000024 RBX: ffff8880ab8aba40 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff814dff01 RDI: ffffed1012a4eef4
RBP: ffff8880952778b8 R08: 0000000000000024 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: ffff88808e1b19c0
R13: 000023d50af30002 R14: ffff8880952778d0 R15: 0000000000000003
nilfs_dat_commit_update+0x26/0x40 fs/nilfs2/dat.c:236
nilfs_direct_propagate fs/nilfs2/direct.c:277 [inline]
nilfs_direct_propagate+0x237/0x2f0 fs/nilfs2/direct.c:256
nilfs_bmap_propagate+0x73/0x170 fs/nilfs2/bmap.c:337
nilfs_collect_file_data+0x45/0xd0 fs/nilfs2/segment.c:573
nilfs_segctor_apply_buffers+0x14a/0x490 fs/nilfs2/segment.c:1014
nilfs_segctor_scan_file+0x3f4/0x6f0 fs/nilfs2/segment.c:1063
nilfs_segctor_collect_blocks fs/nilfs2/segment.c:1170 [inline]
nilfs_segctor_collect fs/nilfs2/segment.c:1494 [inline]
nilfs_segctor_do_construct+0x242b/0x8360 fs/nilfs2/segment.c:2036
nilfs_segctor_construct+0x764/0xae0 fs/nilfs2/segment.c:2372
nilfs_segctor_thread_construct fs/nilfs2/segment.c:2480 [inline]
nilfs_segctor_thread+0x3cb/0xf50 fs/nilfs2/segment.c:2563
kthread+0x33f/0x460 kernel/kthread.c:259
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415
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
syzbot
Oct 1, 2022, 2:00:42 PM10/1/22
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 9d5c0b3a8e1a Linux 4.14.295
syzbot found the following issue on:
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17e103d4880000
kernel config: https://syzkaller.appspot.com/x/.config?x=746c079015a92425
dashboard link: https://syzkaller.appspot.com/bug?extid=0c020101894a4ceb0fe0
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11e61882880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15809d38880000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/ed6fcf5895a2/disk-9d5c0b3a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/341aa3534116/vmlinux-9d5c0b3a.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
IPVS: ftp: loaded support on port[0] = 21
NILFS (loop0): broken superblock, retrying with spare superblock (blocksize = 1024)
NILFS (loop0): segctord starting. Construction interval = 5 seconds, CP frequency < 30 seconds
------------[ cut here ]------------
Kernel panic - not syncing: panic_on_warn set ...
CPU: 1 PID: 8032 Comm: segctord Not tainted 4.14.295-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
Call Trace:
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:964
RIP: 0010:nilfs_dat_commit_end+0x469/0x5c0 fs/nilfs2/dat.c:195
RSP: 0018:ffff8880959a78c0 EFLAGS: 00010297
RAX: ffff8880b3248340 RBX: ffff8880999c9a40 RCX: 1ffff11013510dc9
RDX: 0000000000000000 RSI: 0000000000000012 RDI: ffff88809a8877b8
RBP: ffff8880959a7968 R08: ffff88808d67f7c0 R09: 0000000000000002
R10: 0000000000000000 R11: ffff8880b3248340 R12: ffff88808d67c9c8
R13: ffff8880959a7980 R14: 0000000000000003 R15: 000023d50af30002
nilfs_dat_commit_update+0x26/0x40 fs/nilfs2/dat.c:245
nilfs_direct_propagate fs/nilfs2/direct.c:286 [inline]
nilfs_direct_propagate+0x1d4/0x270 fs/nilfs2/direct.c:265
nilfs_bmap_propagate+0x73/0x160 fs/nilfs2/bmap.c:346
nilfs_collect_file_data+0x41/0xb0 fs/nilfs2/segment.c:582
nilfs_segctor_apply_buffers+0x191/0x450 fs/nilfs2/segment.c:1027
nilfs_segctor_scan_file+0x366/0x630 fs/nilfs2/segment.c:1076
nilfs_segctor_collect_blocks fs/nilfs2/segment.c:1183 [inline]
nilfs_segctor_collect fs/nilfs2/segment.c:1507 [inline]
nilfs_segctor_do_construct+0x20f0/0x78d0 fs/nilfs2/segment.c:2049
nilfs_segctor_construct+0x6db/0x8e0 fs/nilfs2/segment.c:2385
nilfs_segctor_thread_construct fs/nilfs2/segment.c:2493 [inline]
nilfs_segctor_thread+0x3ad/0xdb0 fs/nilfs2/segment.c:2577
kthread+0x30d/0x420 kernel/kthread.c:232
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:404
Reply all
Reply to author
Forward
0 new messages