syzbot


WARNING in nilfs_sufile_set_segment_usage

Status: auto-obsoleted due to no activity on 2023/12/21 09:47
Reported-by: syzbot+972ee0057a42ef3c8949@syzkaller.appspotmail.com
First crash: 619d, last: 513d
Fix bisection: failed (error log, bisect log)
  
Bug presence (1)
Date Name Commit Repro Result
2023/12/21 upstream (ToT) a4aebe936554 C Didn't crash
Similar bugs (3)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-4.14 WARNING in nilfs_sufile_set_segment_usage C 1 630d 630d 0/1 upstream: reported C repro on 2023/03/02 13:59
upstream WARNING in nilfs_sufile_set_segment_usage nilfs C inconclusive 341 364d 782d 25/28 fixed on 2024/01/20 21:18
linux-6.1 WARNING in nilfs_sufile_set_segment_usage origin:upstream C done 4 372d 619d 3/3 fixed on 2023/12/18 16:47
Fix bisection attempts (4)
Created Duration User Patch Repo Result
2023/09/04 06:13 0m bisect fix linux-5.15.y error job log
2023/06/26 21:32 1h07m bisect fix linux-5.15.y OK (0) job log log
2023/05/27 09:31 40m bisect fix linux-5.15.y OK (0) job log log
2023/04/25 21:09 45m bisect fix linux-5.15.y OK (0) job log log

Sample crash report:
NILFS (loop0): segctord starting. Construction interval = 5 seconds, CP frequency < 30 seconds
------------[ cut here ]------------
WARNING: CPU: 1 PID: 3588 at fs/nilfs2/sufile.c:539 nilfs_sufile_set_segment_usage+0x4fd/0x5e0
Modules linked in:
CPU: 1 PID: 3588 Comm: segctord Not tainted 5.15.104-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
RIP: 0010:nilfs_sufile_set_segment_usage+0x4fd/0x5e0 fs/nilfs2/sufile.c:539
Code: 04 25 28 00 00 00 48 3b 84 24 a0 00 00 00 0f 85 f3 00 00 00 89 d8 48 8d 65 d8 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 f3 22 59 fe <0f> 0b e9 0f fe ff ff e8 e7 22 59 fe e8 e2 f1 d9 fd e9 be fe ff ff
RSP: 0018:ffffc90002cef640 EFLAGS: 00010293
RAX: ffffffff832694ed RBX: 0000000000000004 RCX: ffff8880243a1d00
RDX: 0000000000000000 RSI: 0000000000000004 RDI: 0000000000000000
RBP: ffffc90002cef730 R08: ffffffff832692f0 R09: ffffffff8321bc10
R10: 0000000000000002 R11: ffff8880243a1d00 R12: dffffc0000000000
R13: ffff88801a55a000 R14: ffff888073b625e8 R15: 0000000000000060
FS:  0000000000000000(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fa940e03428 CR3: 000000000c68e000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 nilfs_segctor_update_segusage fs/nilfs2/segment.c:1447 [inline]
 nilfs_segctor_do_construct+0x4d10/0x7410 fs/nilfs2/segment.c:2071
 nilfs_segctor_construct+0x145/0x8c0 fs/nilfs2/segment.c:2381
 nilfs_segctor_thread_construct fs/nilfs2/segment.c:2489 [inline]
 nilfs_segctor_thread+0x54c/0x1140 fs/nilfs2/segment.c:2572
 kthread+0x3f6/0x4f0 kernel/kthread.c:319
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
 </TASK>

Crashes (2):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/03/26 21:09 linux-5.15.y 115472395b0a fbf0499a .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan WARNING in nilfs_sufile_set_segment_usage
2023/03/13 03:07 linux-5.15.y bbf9f29bac04 5205ef30 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan-arm64 WARNING in nilfs_sufile_set_segment_usage
* Struck through repros no longer work on HEAD.