umount.2: Correct the description of MNT_DETACH

I recently realized that I had been reasoning improperly about
what umount(MNT_DETACH) did based on an insufficient description
in the umount.2 man page, that matched my intuition but not the
implementation.

When there are no submounts, MNT_DETACH is essentially harmless to
applications.  Where there are submounts, MNT_DETACH changes what
is visible to applications using the detach directories.

Signed-off-by: Eric W. Biederman <ebiederm@xmission.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Eric W. Biederman 2014-09-29 18:04:05 -07:00 committed by Michael Kerrisk
parent 3ef9fdd1a9
commit f131122173
1 changed files with 4 additions and 3 deletions

View File

@ -66,9 +66,10 @@ This can cause data loss.
(Only for NFS mounts.) (Only for NFS mounts.)
.TP .TP
.BR MNT_DETACH " (since Linux 2.4.11)" .BR MNT_DETACH " (since Linux 2.4.11)"
Perform a lazy unmount: make the mount point unavailable for Perform a lazy unmount: make the mount point unavailable for new
new accesses, and actually perform the unmount when the mount point accesses, immediately disconnect the filesystem and all filesystems
ceases to be busy. mounted below it from each other and from the mount table, and
actually perform the unmount when the mount point ceases to be busy.
.TP .TP
.BR MNT_EXPIRE " (since Linux 2.6.8)" .BR MNT_EXPIRE " (since Linux 2.6.8)"
Mark the mount point as expired. Mark the mount point as expired.