Date: Sun, 05 Feb 2023 01:07:28 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 269328] nfs client: data corruption using fspacectl and mmap Message-ID: <bug-269328-227-L42FYUdfcL@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-269328-227@https.bugs.freebsd.org/bugzilla/> References: <bug-269328-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=3D269328 --- Comment #1 from Rick Macklem <rmacklem@FreeBSD.org> --- I wonder if 3b6056204dd8 that was just committed by kib@ might fix this? For a 13.1 server (which does not support the Deallocate operation), the client uses vop_stddeallocate() and it uses vn_bmap_seekhole_locked(). If it doesn't fix the problem, then I'd guess nfs_deallocate() needs a fix for the generic case where it calls vop_stddeallocate(). nfs_deallocate() does call vnode_pager_purge_range() before doing the RPC, but that won't happen against a 13.1 server. It's not clear to me how vnode_pager_purge_range() compares to doing a vm_object_page_clean()? I'll try to test against a 14 server that supports Deallocate. If you can test with a client with 3b6056204dd8 and let us know if it helps, that would be nice. --=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-269328-227-L42FYUdfcL>