Date: Sun, 07 Jan 2024 22:19:57 +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-DkAgTAF89b@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 #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 =3D true [weights] truncate =3D 0 fsync =3D 1 fdatasync =3D 1 punch_hole =3D 0 sendfile =3D 0 write =3D 10 read =3D 10 copy_file_range =3D 0 --=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-DkAgTAF89b>