From f6aaf493f8640844230c1959d71a9f33f2dcdc26 Mon Sep 17 00:00:00 2001 From: Michael Kerrisk Date: Thu, 19 Aug 2021 00:42:40 +0200 Subject: [PATCH] mount_namespaces.7: wfix Reported-by: Eric W. Biederman Signed-off-by: Michael Kerrisk --- man7/mount_namespaces.7 | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/man7/mount_namespaces.7 b/man7/mount_namespaces.7 index 86c585ec8..1f9888a07 100644 --- a/man7/mount_namespaces.7 +++ b/man7/mount_namespaces.7 @@ -1130,7 +1130,7 @@ which is the error that the kernel returns to indicate that the mount is locked. .IP * Following on from the previous point, -note that it is possible to unmount an entire tree of mounts that +note that it is possible to unmount an entire subtree of mounts that propagated as a unit into a less privileged mount namespace, as illustrated in the following example. .IP @@ -1207,7 +1207,7 @@ ns3# \fBgrep /mnt /proc/self/mountinfo | sed \(aqs/ \- .*//\(aq\fP .IP Because the propagation type of the parent mount, .IR /mnt , -was shared, the recursive bind mount propagated a small tree of +was shared, the recursive bind mount propagated a small subtree of mounts under the slave mount .I /mnt into "ns2", @@ -1227,7 +1227,7 @@ ns2# \fBgrep /mnt /proc/self/mountinfo | sed \(aqs/ \- .*//\(aq\fP While it is not possible to unmount a part of the propagated subtree .RI ( /mnt/ppp/y ) in "ns2", -it is possible to unmount the entire tree, +it is possible to unmount the entire subtree, as shown by the following commands: .IP .in +4n