Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 08 Mar 2019 22:46:36 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 236405] [fuse] FUSE(4) does not send FUSE_FLUSH on close(2)
Message-ID:  <bug-236405-227@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D236405

            Bug ID: 236405
           Summary: [fuse] FUSE(4) does not send FUSE_FLUSH on close(2)
           Product: Base System
           Version: CURRENT
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Many People
          Priority: ---
         Component: kern
          Assignee: bugs@FreeBSD.org
          Reporter: asomers@FreeBSD.org

The FUSE protocol requires the client to send a FUSE_FLUSH command on every
close(2).  The main documented purpose is for filesystems to return delayed
write errors during close (discussed in bug 236327), but a more important,
undocumented purpose is to allow filesystems to release file locks.  That
behavior has been part of the protocol since version 7.7.

--=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-236405-227>