Skip to content

Commit ccbd0c9

Browse files
ratabrauner
authored andcommitted
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/[email protected] Reviewed-by: Christian Brauner (Microsoft) <[email protected]> Signed-off-by: Rodrigo Campos <[email protected]> Signed-off-by: Christian Brauner (Microsoft) <[email protected]>
1 parent af2d861 commit ccbd0c9

File tree

1 file changed

+5
-0
lines changed

1 file changed

+5
-0
lines changed

Documentation/filesystems/idmappings.rst

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -369,6 +369,11 @@ kernel maps the caller's userspace id down into a kernel id according to the
369369
caller's idmapping and then maps that kernel id up according to the
370370
filesystem's idmapping.
371371

372+
Let's see some examples with caller/filesystem idmapping but without mount
373+
idmappings. This will exhibit some problems we can hit. After that we will
374+
revisit/reconsider these examples, this time using mount idmappings, to see how
375+
they can solve the problems we observed before.
376+
372377
Example 1
373378
~~~~~~~~~
374379

0 commit comments

Comments
 (0)