Lines Matching full:mounted

13    might be needed are mounted.  Processes that try to access those
39 filesystem type.  Several "autofs" filesystems can be mounted and they
62 directory is a mount trap only if the filesystem is mounted *direct*
66 filesystem is mounted *indirect* and they are empty.
95 should be mounted on the directory and to return it.  The VFS is
120 Firstly, before checking to see if any filesystem is mounted on the
129    expiry (automatic unmounting of the mounted filesystem) to
144    filesystem can be mounted below the first and for both of them to
176 be mounted or RCU-walk cannot handle the path.
182 would be safe to follow down into any mounted directory and the only
189 mounted, it *will* fall back to REF-walk.  `d_manage()` cannot make the
195 mounted filesystem, otherwise it should return 0.
208 mounted.  As autofs doesn't return such a filesystem but leaves the
222 unmount any filesystems mounted on the autofs filesystem or remove any
262 that has been mounted on instead of considering the top-level names.
272 mounted, though this check is ignored in some cases. It also checks if
283 automount daemon needs to unmount any filesystems mounted below the
310 When an autofs filesystem is mounted the pgid of the mounting
320 When an autofs filesystem is mounted, the 'write' end of a pipe must
437 particularly a *direct* mounted filesystem.  If the automount daemon
503 	name within the filesystem that has been auto-mounted on.
541 When the filesystem is mounted a _uid_ and _gid_ can be given which
571 always be mounted "shared". e.g. ::