Date: Sat, 30 Dec 2023 14:23:09 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 276002] nfscl: data corruption using both copy_file_range and mmap'd I/O Message-ID: <bug-276002-3630-oVv7Wu2u3v@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-276002-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-276002-3630@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 #20 from Alan Somers <asomers@FreeBSD.org> --- (In reply to Konstantin Belousov from comment #19) > But if nomsyncafterwrite is set, is there an inconsistency even without copy_file_range? Yes. > For the second part, I mean that most likely this knobs works because msy= ncs > are interlined with writes, and really msync affects the next write resul= t, > not the previous. --=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-3630-oVv7Wu2u3v>