Date: Fri, 12 Apr 2019 19:05:31 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 235774] [FUSEFS]: Need to evict invalidated cache contents on fuse_write_directbackend() Message-ID: <bug-235774-3630-5qFn0xHLHA@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-235774-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-235774-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=3D235774 --- Comment #5 from commit-hook@freebsd.org --- A commit references this bug: Author: asomers Date: Fri Apr 12 19:05:08 UTC 2019 New revision: 346162 URL: https://svnweb.freebsd.org/changeset/base/346162 Log: fusefs: evict invalidated cache contents during write-through fusefs's default cache mode is "writethrough", although it currently works more like "write-around"; writes bypass the cache completely. Since writ= es bypass the cache, they were leaving stale previously-read data in the cac= he. This commit invalidates that stale data. It also adds a new global v_inval_buf_range method, like vtruncbuf but for a range of a file. PR: 235774 Reported by: cem Sponsored by: The FreeBSD Foundation Changes: projects/fuse2/sys/fs/fuse/fuse_io.c projects/fuse2/sys/kern/vfs_subr.c projects/fuse2/sys/sys/vnode.h projects/fuse2/tests/sys/fs/fusefs/write.cc --=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-235774-3630-5qFn0xHLHA>