panic: ffs_fsync: not dirty

Status: auto-obsoleted due to no activity on 2024/07/20 09:41
Reported-by: syzbot+b51d6659984cb432d4ee@syzkaller.appspotmail.com
First crash: 870d, last: 860d

Sample crash report:
login: panic: ffs_fsync: not dirty
Starting stack trace...
panic(ffffffff829331ac) at panic+0x16f sys/kern/subr_prf.c:229
ffs_fsync(ffff80002a166f40) at ffs_fsync+0x387 sys/ufs/ffs/ffs_vnops.c:447
VOP_FSYNC(fffffd80788f8888,fffffd807f7d7ea0,3,ffff80002a148cd8) at VOP_FSYNC+0xd2 sys/kern/vfs_vops.c:311
syncer_thread(ffff80002a148cd8) at syncer_thread+0x221 sys/kern/vfs_sync.c:161
end trace frame: 0x0, count: 253
End of stack trace.

Crashes (3):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/04/21 09:40 openbsd a0c63bf7b3c7 af24b050 .config console log report ci-openbsd-multicore panic: ffs_fsync: not dirty
2024/04/16 00:07 openbsd 9dcb0c6dfd57 0d592ce4 .config console log report ci-openbsd-multicore panic: ffs_fsync: not dirty
2024/04/11 06:12 openbsd d11f3b71804f 33b9e058 .config console log report [disk image] [bsd.gdb] [kernel image] ci-openbsd-multicore panic: ffs_fsync: not dirty
* Struck through repros no longer work on HEAD.