summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRodrigo Campos <rodrigo@sdfg.com.ar>2022-04-29 15:57:48 +0200
committerChristian Brauner (Microsoft) <brauner@kernel.org>2022-05-09 11:20:43 +0200
commitccbd0c991985afc53670e2b01840517922fc30e4 (patch)
treedd6bfa041b4bc2ed78839bb75a37c89b519431f6
parentaf2d861d4cd2a4da5137f795ee3509e6f944a25b (diff)
downloadlwn-ccbd0c991985afc53670e2b01840517922fc30e4.tar.gz
lwn-ccbd0c991985afc53670e2b01840517922fc30e4.zip
docs: Add small intro to idmap examples
When reading the documentation, I didn't understand why this list examples of things that fail without using the mount idmap feature. It seems pretty pointless and I doubted if I was missing something, until I finished the examples, the next section and saw the examples revisited. After that, it all made sense. Let's add one small sentence before, so the reader knows where this is going and why examples that don't might seem relevant are used. Link: https://lore.kernel.org/r/20220429135748.481301-1-rodrigo@sdfg.com.ar Reviewed-by: Christian Brauner (Microsoft) <brauner@kernel.org> Signed-off-by: Rodrigo Campos <rodrigo@sdfg.com.ar> Signed-off-by: Christian Brauner (Microsoft) <brauner@kernel.org>
-rw-r--r--Documentation/filesystems/idmappings.rst5
1 files changed, 5 insertions, 0 deletions
diff --git a/Documentation/filesystems/idmappings.rst b/Documentation/filesystems/idmappings.rst
index 7a879ec3b6bf..c1db8748389c 100644
--- a/Documentation/filesystems/idmappings.rst
+++ b/Documentation/filesystems/idmappings.rst
@@ -369,6 +369,11 @@ kernel maps the caller's userspace id down into a kernel id according to the
caller's idmapping and then maps that kernel id up according to the
filesystem's idmapping.
+Let's see some examples with caller/filesystem idmapping but without mount
+idmappings. This will exhibit some problems we can hit. After that we will
+revisit/reconsider these examples, this time using mount idmappings, to see how
+they can solve the problems we observed before.
+
Example 1
~~~~~~~~~