view Documentation/filesystems/automount-support.txt @ 524:7f8b544237bf

netfront: Allow netfront in domain 0.

This is useful if your physical network device is in a utility domain.

Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
author Keir Fraser <keir.fraser@citrix.com>
date Tue Apr 15 15:18:58 2008 +0100 (2008-04-15)
parents 831230e53067
line source
1 Support is available for filesystems that wish to do automounting support (such
2 as kAFS which can be found in fs/afs/). This facility includes allowing
3 in-kernel mounts to be performed and mountpoint degradation to be
4 requested. The latter can also be requested by userspace.
7 ======================
9 ======================
11 A filesystem can now mount another filesystem on one of its directories by the
12 following procedure:
14 (1) Give the directory a follow_link() operation.
16 When the directory is accessed, the follow_link op will be called, and
17 it will be provided with the location of the mountpoint in the nameidata
18 structure (vfsmount and dentry).
20 (2) Have the follow_link() op do the following steps:
22 (a) Call vfs_kern_mount() to call the appropriate filesystem to set up a
23 superblock and gain a vfsmount structure representing it.
25 (b) Copy the nameidata provided as an argument and substitute the dentry
26 argument into it the copy.
28 (c) Call do_add_mount() to install the new vfsmount into the namespace's
29 mountpoint tree, thus making it accessible to userspace. Use the
30 nameidata set up in (b) as the destination.
32 If the mountpoint will be automatically expired, then do_add_mount()
33 should also be given the location of an expiration list (see further
34 down).
36 (d) Release the path in the nameidata argument and substitute in the new
37 vfsmount and its root dentry. The ref counts on these will need
38 incrementing.
40 Then from userspace, you can just do something like:
42 [root@andromeda root]# mount -t afs \#root.afs. /afs
43 [root@andromeda root]# ls /afs
44 asd cambridge cambridge.redhat.com grand.central.org
45 [root@andromeda root]# ls /afs/cambridge
46 afsdoc
47 [root@andromeda root]# ls /afs/cambridge/afsdoc/
48 ChangeLog html LICENSE pdf RELNOTES-1.2.2
50 And then if you look in the mountpoint catalogue, you'll see something like:
52 [root@andromeda root]# cat /proc/mounts
53 ...
54 #root.afs. /afs afs rw 0 0
55 #root.cell. /afs/cambridge.redhat.com afs rw 0 0
56 #afsdoc. /afs/cambridge.redhat.com/afsdoc afs rw 0 0
59 ===========================
61 ===========================
63 Automatic expiration of mountpoints is easy, provided you've mounted the
64 mountpoint to be expired in the automounting procedure outlined above.
66 To do expiration, you need to follow these steps:
68 (3) Create at least one list off which the vfsmounts to be expired can be
69 hung. Access to this list will be governed by the vfsmount_lock.
71 (4) In step (2c) above, the call to do_add_mount() should be provided with a
72 pointer to this list. It will hang the vfsmount off of it if it succeeds.
74 (5) When you want mountpoints to be expired, call mark_mounts_for_expiry()
75 with a pointer to this list. This will process the list, marking every
76 vfsmount thereon for potential expiry on the next call.
78 If a vfsmount was already flagged for expiry, and if its usage count is 1
79 (it's only referenced by its parent vfsmount), then it will be deleted
80 from the namespace and thrown away (effectively unmounted).
82 It may prove simplest to simply call this at regular intervals, using
83 some sort of timed event to drive it.
85 The expiration flag is cleared by calls to mntput. This means that expiration
86 will only happen on the second expiration request after the last time the
87 mountpoint was accessed.
89 If a mountpoint is moved, it gets removed from the expiration list. If a bind
90 mount is made on an expirable mount, the new vfsmount will not be on the
91 expiration list and will not expire.
93 If a namespace is copied, all mountpoints contained therein will be copied,
94 and the copies of those that are on an expiration list will be added to the
95 same expiration list.
98 =======================
100 =======================
102 As an alternative, it is possible for userspace to request expiry of any
103 mountpoint (though some will be rejected - the current process's idea of the
104 rootfs for example). It does this by passing the MNT_EXPIRE flag to
105 umount(). This flag is considered incompatible with MNT_FORCE and MNT_DETACH.
107 If the mountpoint in question is in referenced by something other than
108 umount() or its parent mountpoint, an EBUSY error will be returned and the
109 mountpoint will not be marked for expiration or unmounted.
111 If the mountpoint was not already marked for expiry at that time, an EAGAIN
112 error will be given and it won't be unmounted.
114 Otherwise if it was already marked and it wasn't referenced, unmounting will
115 take place as usual.
117 Again, the expiration flag is cleared every time anything other than umount()
118 looks at a mountpoint.