Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 30 Dec 2023 03:51:13 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 276002] nfscl: data corruption using both copy_file_range and mmap'd I/O
Message-ID:  <bug-276002-227-iYL9zUvRJ9@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-276002-227@https.bugs.freebsd.org/bugzilla/>
References:  <bug-276002-227@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D276002

--- Comment #18 from Alan Somers <asomers@FreeBSD.org> ---
(In reply to Konstantin Belousov from comment #17)
I've tried it both ways.  Whether or not copy_file_range is enabled, if
nomsyncafterwrite is not set, then there is no crash.

And nomsyncafterwrite refers to msync immediately after mapped write.

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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-276002-227-iYL9zUvRJ9>