Date: Mon, 01 Jan 2024 15:48:32 +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-LZ1fvndiIt@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 #32 from Rick Macklem <rmacklem@FreeBSD.org> --- Righto. To be honest, this may not be fixable, given the way NFS does I/O below the buffer cache (no vnode lock, etc). The fix may be to document the need to use msync(2) when mmap'd I/O is mixed with syscall I/O for NFS mounts. --> An update to the msync man page maybe? --=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-LZ1fvndiIt>