Lines Matching refs:mount

15 are things such as setting an autofs mount catatonic, setting the
18 mount itself which prevents us being able to use open(2) to obtain a
23 needs to walk back up the mount tree to construct a path, such as
26 from the mount tree.
31 because autofs direct mounts and the implementation of "on demand mount
32 and expire" of nested mount trees have the file system mounted directly
33 on top of the mount trigger directory dentry.
37 a direct mount in disguise) and indirect.
60 operation. So we see a mount of shark:/autofs/export1 on /test/g1, for
63 The way that direct mounts are handled is by making an autofs mount on
64 each full path, such as /automount/dparse/g1, and using it as a mount
65 trigger. So when we walk on the path we mount shark:/autofs/export1 "on
66 top of this mount point". Since these are always directories we can
67 use the follow_link inode operation to trigger the mount.
70 them multi-mount map entries).
72 For example, an indirect mount map entry could also be:
81 and a similarly a direct mount map entry could also be:
92 to mount and umount all of the offsets as a single unit. Not really a
98 In version 5 we mount only as we go down the tree of offsets and
103 above and so the mount points can be covered by a mount.
106 on the mount point for control operations. The references held by the
107 descriptor are accounted for in checks made to determine if a mount is
109 in the mount super block. So the use of a file handle needs to be
118 for these potentially covered autofs mount points. Rather than just
123 In addition, to be able to reconstruct a mount tree that has busy mounts,
124 the uid and gid of the last user that triggered the mount needs to be
126 autofs maps. They are recorded at mount request time and an operation
131 a mount or expire operation completes a status is returned to the
136 very large maps, is discovering if a mount is present. Usually this
139 in the mount table. An operation to lookup the mount status of a mount
156 the mount table which has proved to be a big overhead for users with
159 issued for a mount (file handle) we should continually call back to
162 mount at a time. A Generic Netlink implementation would exclude this
167 autofs4 Miscellaneous Device mount control interface
188 The ioctlfd field is a mount point file descriptor of an autofs mount
190 the check for whether a given path is a mount point, where it may
191 optionally be used to check a specific mount corresponding to a given
192 mount point file descriptor, and when requesting the uid and gid of the
193 last successful mount on a directory within the autofs file system.
216 not a valid descriptor or doesn't correspond to an autofs mount point
247 with the ioctlfd field set to a valid autofs mount point descriptor
256 Obtain and release a file descriptor for an autofs managed mount point
259 as the arg1 field set to the device number of the autofs mount. The
260 device number can be obtained from the mount options shown in
272 Return mount and expire result status from user space to the kernel.
276 by user space in the foregoing mount or expire request. The arg2 field
285 Normally this is set at mount time using an option but when reconnecting
286 to a existing mount we need to use this to tell the autofs mount about
289 mount be catatonic (see next call).
301 Make the autofs mount point catatonic. The autofs mount will no longer
302 issue mount requests, the kernel communication pipe descriptor is released
312 Set the expire timeout for mounts within an autofs mount point.
322 mount on the given path dentry.
325 field set to the mount point in question and the size field adjusted
327 containing autofs mount. Upon return the struct field arg1 contains the
330 When reconstructing an autofs mount tree with active mounts we need to
332 gid (or string variations of them) for mount lookups within the map entry.
334 used by user space for the mount map lookups.
340 Issue an expire request to the kernel for an autofs mount. Typically
345 addition an immediate expire, independent of the mount timeout, can be
349 This call causes the kernel module to check the mount corresponding
356 Checks if an autofs mount point is in use.
369 possible variations. Both use the path field set to the path of the mount
371 ioctlfd field to identify a specific mount point to check while the other
372 variation uses the path and optionally arg1 set to an autofs mount type.
373 The call returns 1 if this is a mount point and sets arg1 to the device
374 number of the mount and field arg2 to the relevant super block magic
379 If supplied with a file descriptor we're looking for a specific mount,
382 a mountpoint or contains a mount, such as a multi-mount without a root
383 mount. In this case we return 1 if the descriptor corresponds to a mount
384 point and and also returns the super magic of the covering mount if there
388 is looked up and is checked to see if it is the root of a mount. If a
389 type is also given we are looking for a particular autofs mount and if
391 root of a mount 1 is returned along with the super magic of the mount