[Bug 276002] nfscl: data corruption using both copy_file_range and mmap'd I/O

From: <bugzilla-noreply_at_freebsd.org>
Date: Sun, 07 Jan 2024 22:19:57 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276002

--- Comment #52 from Alan Somers <asomers@FreeBSD.org> ---
With the latest code in main, including kib's two commits, I can no longer
reproduce the bug using the second copy_file_range.toml file I posted.  But I
can still reproduce it using the original file.  In fact, I can reproduce it
without using copy_file_range or truncate at all, using this config file.  This
may be a different bug:

nomsyncafterwrite = true
[weights]
truncate = 0
fsync = 1
fdatasync = 1
punch_hole = 0
sendfile = 0
write = 10
read = 10
copy_file_range = 0

-- 
You are receiving this mail because:
You are the assignee for the bug.