From: "Göran Uddeborg" <goeran@uddeborg.se>
To: Alejandro Colomar <alx@kernel.org>
Cc: <linux-man@vger.kernel.org>
Subject: [PATCH] man/man7/mount_namespaces.7: Fix an incorrect path in an example
Date: Sun, 16 Feb 2025 19:59:50 +0100 [thread overview]
Message-ID: <26546.13734.573762.288144@gargle.gargle.HOWL> (raw)
[-- Attachment #1: Type: text/plain, Size: 1034 bytes --]
In the example showing how locked mounts in a less privileged mount
namespace can not be split, first /etc/shadow is bind mounted, then an
attempt is done to unmount /mnt/dir, which gives an error complaining
that /etc/shadow is not mounted. The unmount should also refer to
/etc/shadow.
Signed-off-by: Göran Uddeborg <goeran@uddeborg.se>
---
man/man7/mount_namespaces.7 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/man/man7/mount_namespaces.7 b/man/man7/mount_namespaces.7
index a1645e9e2..0e1223f99 100644
--- a/man/man7/mount_namespaces.7
+++ b/man/man7/mount_namespaces.7
@@ -1128,7 +1128,7 @@ .SS Restrictions on mount namespaces
.EX
# \fBunshare \-\-user \-\-map\-root\-user \-\-mount \[rs]\fP
\fBstrace \-o /tmp/log \[rs]\fP
- \fBumount /mnt/dir\fP
+ \fBumount /etc/shadow\fP
umount: /etc/shadow: not mounted.
# \fBgrep \[aq]\[ha]umount\[aq] /tmp/log\fP
umount2("/etc/shadow", 0) = \-1 EINVAL (Invalid argument)
--
2.40.1
[-- Attachment #2: Type: application/pgp-signature, Size: 862 bytes --]
next reply other threads:[~2025-02-16 19:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-16 18:59 Göran Uddeborg [this message]
2025-02-16 20:03 ` [PATCH] man/man7/mount_namespaces.7: Fix an incorrect path in an example Alejandro Colomar
2025-02-16 21:49 ` Göran Uddeborg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=26546.13734.573762.288144@gargle.gargle.HOWL \
--to=goeran@uddeborg.se \
--cc=alx@kernel.org \
--cc=linux-man@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox