Lines Matching +full:non +full:- +full:sticky

1 .. SPDX-License-Identifier: GPL-2.0
18 Non-privileged mount (or user mount):
19 A userspace filesystem mounted by a non-privileged (non-root) user.
45 non-privileged mounts. This opens up new possibilities for the use of
111 mount -t fusectl none /sys/fs/fuse/connections
124 no filesystem activity and 'waiting' is non-zero, then the
140 - If the request is not yet sent to userspace AND the signal is
144 - If the request is not yet sent to userspace AND the signal is not
149 - If the request is already sent to userspace, then an INTERRUPT
193 - Kill the filesystem daemon. Works in case of a) and b)
195 - Kill the filesystem daemon and all users of the filesystem. Works
198 - Use forced umount (umount -f). Works in all cases but only if
201 - Abort filesystem through the FUSE control filesystem. Most
204 How do non-privileged mounts work?
210 The implication of providing non-privileged mounts is that the mount
235 for non-privileged mounts.
255 access to the mountpoint, and mountpoint is not a "sticky"
290 measures, that system processes will never enter non-privileged
293 - With the 'user_allow_other' config option. If this config option is
298 an unprivileged user - normally restricted from mounting with
299 'allow_other' - could do so in a user namespace where they're
306 - With the 'allow_sys_admin_access' module option. If this option is
312 information leak or *DoS* as described in points B and C/2/i-ii in the
315 Kernel - userspace interface
327 | | [sleep on fc->waitq]
332 | fc->unused_list] |
334 | [queue req on fc->pending] |
335 | [wake up fc->waitq] | [woken up]
337 | [sleep on req->waitq] |
339 | | [remove req from fc->pending]
341 | | [add req to fc->processing]
349 | | [look up req in fc->processing]
350 | | [remove from fc->processing]
352 | [woken up] | [wake up req->waitq]
358 | fc->unused_list] |
368 **Scenario 1 - Simple deadlock**::
376 | [sleep on req->waitq] |
385 **Scenario 2 - Tricky deadlock**
403 | [sleep on req->waitq] |
406 | | >sys_write(addr - headerlength)
408 | | [look up req in fc->processing]
409 | | [remove from fc->processing]
425 get_user_pages(). The 'req->locked' flag indicates when the copy is