Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 14 Mar 2019 16:48:59 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 236530] [FUSE] most fuse syscalls should be interruptible
Message-ID:  <bug-236530-227@https.bugs.freebsd.org/bugzilla/>

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

            Bug ID: 236530
           Summary: [FUSE] most fuse syscalls should be interruptible
           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

A FUSE filesystem daemon runs in userland and is allowed to do very slow st=
uff,
like access the network, for any operation.  Accordingly, any syscall that
waits on a response from the daemon should be interruptible, so any
unresponsive daemon won't cause a system hang.

The FUSE protocol includes a mechanism for interrupting operations.  It's
described in detail in doc/kernel.txt within the libfuse sources.  Our driv=
er
currently doesn't implement it, but it should.

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