Date: Thu, 25 Mar 2021 01:12:03 +0000 From: bugzilla-noreply@freebsd.org To: gnome@FreeBSD.org Subject: [Bug 254452] [fusefs] [devel/gvfs]: gvfsd-fuse needs FUSE_CAP_ATOMIC_O_TRUNC from fuse Message-ID: <bug-254452-6497-RiAXpglDAT@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-254452-6497@https.bugs.freebsd.org/bugzilla/> References: <bug-254452-6497@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=3D254452 --- Comment #3 from Damjan Jovanovic <damjan.jov@gmail.com> --- (In reply to Alan Somers from comment #1) gvfsd-fuse exports gio operations on its virtual filesystems over FUSE, and= in gio O_APPEND becomes g_file_append_to(), O_TRUNC becomes g_file_replace(), = and there is no API - by design - for opening a file to write without either of those flags; it fails with ENOTSUP. Even with gvfs patched to remove FUSE_CAP_ATOMIC_O_TRUNC, the result is that files cannot be overwritten. This would be difficult to fix inside gvfsd-fuse, and might not be accepted upstream. Can't our VFS layer be patched to delegate open()/create() flags = to filesystems that support them? gvfs is an important and widely used desktop package. --=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-254452-6497-RiAXpglDAT>