ci2 starts bisection 2023-01-28 14:22:35.388101425 +0000 UTC m=+434046.368684873 bisecting fixing commit since 4fe89d07dcc2804c8b562f6c7896a45643d34b2f building syzkaller on feb5635181eb12a6e3516172a3f5af06a3bc93e1 ensuring issue is reproducible on original commit 4fe89d07dcc2804c8b562f6c7896a45643d34b2f testing commit 4fe89d07dcc2804c8b562f6c7896a45643d34b2f gcc compiler: Debian clang version 13.0.1-6~deb11u1, GNU ld (GNU Binutils for Debian) 2.35.2 kernel signature: f52b563c7e11d0162b8a4b583fd7a943e612dba74e0898ac9d380d6cec53cd4f all runs: crashed: WARNING in nilfs_sufile_set_segment_usage testing current HEAD 5af6ce7049365952f7f023155234fe091693ead1 testing commit 5af6ce7049365952f7f023155234fe091693ead1 gcc compiler: Debian clang version 13.0.1-6~deb11u1, GNU ld (GNU Binutils for Debian) 2.35.2 kernel signature: 4c26c21c3aa3620abf0744bdec4843ed1a5ec705547937b45e83f0f2a4859f14 run #0: basic kernel testing failed: BUG: program execution failed: executor NUM: exit status NUM run #1: crashed: WARNING in nilfs_sufile_set_segment_usage run #2: crashed: WARNING in nilfs_sufile_set_segment_usage run #3: crashed: WARNING in nilfs_sufile_set_segment_usage run #4: crashed: WARNING in nilfs_sufile_set_segment_usage run #5: crashed: WARNING in nilfs_sufile_set_segment_usage run #6: crashed: WARNING in nilfs_sufile_set_segment_usage run #7: crashed: WARNING in nilfs_sufile_set_segment_usage run #8: crashed: WARNING in nilfs_sufile_set_segment_usage run #9: crashed: WARNING in nilfs_sufile_set_segment_usage revisions tested: 2, total time: 42m32.580665704s (build: 33m40.00267184s, test: 6m48.756352811s) the crash still happens on HEAD commit msg: Merge tag '6.2-rc5-smb3-client-fixes' of git://git.samba.org/sfrench/cifs-2.6 crash: WARNING in nilfs_sufile_set_segment_usage NILFS (loop0): segctord starting. Construction interval = 5 seconds, CP frequency < 30 seconds ------------[ cut here ]------------ WARNING: CPU: 0 PID: 5580 at fs/nilfs2/sufile.c:539 nilfs_sufile_set_segment_usage+0x44c/0x540 fs/nilfs2/sufile.c:551 Modules linked in: CPU: 0 PID: 5580 Comm: segctord Not tainted 6.2.0-rc5-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/12/2023 RIP: 0010:nilfs_sufile_set_segment_usage+0x44c/0x540 fs/nilfs2/sufile.c:539 Code: 00 00 65 48 8b 04 25 28 00 00 00 48 3b 84 24 a0 00 00 00 0f 85 f4 00 00 00 89 d8 48 8d 65 d8 5b 41 5c 41 5d 41 5e 41 5f 5d c3 <0f> 0b e9 84 fe ff ff e8 68 94 f7 fd e9 0a ff ff ff 89 f9 80 e1 07 RSP: 0018:ffffc90004d2f5c0 EFLAGS: 00010202 RAX: 1ffff1100e9b8400 RBX: ffff888074dc205c RCX: 0000000000000040 RDX: dffffc0000000000 RSI: 0000000000000004 RDI: ffff8880169610a8 RBP: ffffc90004d2f6b0 R08: dffffc0000000000 R09: ffffed100e442d69 R10: ffffed100e442d69 R11: 1ffff1100e442d68 R12: 0000000000000050 R13: ffff88807231a5e8 R14: 1ffff920009a5ec4 R15: ffff888074dc2000 FS: 0000000000000000(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007faaad820a70 CR3: 000000000bc8e000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: nilfs_segctor_update_segusage fs/nilfs2/segment.c:1447 [inline] nilfs_segctor_do_construct+0x372b/0x6120 fs/nilfs2/segment.c:2071 nilfs_segctor_construct+0x11e/0x760 fs/nilfs2/segment.c:2379 nilfs_segctor_thread_construct fs/nilfs2/segment.c:2487 [inline] nilfs_segctor_thread+0x61b/0xf50 fs/nilfs2/segment.c:2570 kthread+0x228/0x2a0 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308