Lines Matching full:daemon

12 involve communication between the kernel and a userspace FUSE daemon, which can
14 the userspace daemon and be executed directly by the kernel on an underlying
17 This is achieved by the FUSE daemon registering a file descriptor (pointing to
20 When a FUSE file is subsequently opened, the FUSE daemon can, in its response to
35   2. The FUSE daemon, during the ``FUSE_INIT`` handshake, must negotiate the
38   3. The (privileged) FUSE daemon uses the ``FUSE_DEV_IOC_BACKING_OPEN`` ioctl
41   4. When handling an ``OPEN`` or ``CREATE`` request for a FUSE file, the daemon
45   5. The FUSE daemon should eventually call ``FUSE_DEV_IOC_BACKING_CLOSE`` with
52 Setting up passthrough functionality currently requires the FUSE daemon to
61 The core mechanism for passthrough involves the FUSE daemon opening a file
67 A significant concern arises because the FUSE daemon can close its own file
76      daemon closes its file descriptor, the open backing file held by the kernel
83   2. **Bypassing RLIMIT_NOFILE**: The FUSE daemon process is subject to
85      (``RLIMIT_NOFILE``). If an unprivileged daemon could register backing files
88      accounted against the daemon's ``RLIMIT_NOFILE``. This could lead to a
116 For example, during the ``FUSE_INIT`` handshake, the FUSE daemon can negotiate