Date: Sun, 16 Feb 2020 23:23:52 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 244178] [FUSEFS]: underlying file modified leads to corrupted fuse data Message-ID: <bug-244178-227-cAAbM6JRIU@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-244178-227@https.bugs.freebsd.org/bugzilla/> References: <bug-244178-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=3D244178 --- Comment #1 from Alan Somers <asomers@FreeBSD.org> --- In step 5, are you extending the underlying file from EOF onwards, or are y= ou rewriting the whole thing? And in step 7, is the data correct up until the= old EOF, or is it all wrong? Do you have a standalone test case that can demonstrate the problem? It sounds to me like the correct answer might be for the fuse server to ret= urn FOPEN_DIRECT_IO for every FUSE_OPEN request. That would prevent the kernel from using the cache at all. --=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-244178-227-cAAbM6JRIU>