Lines Matching refs:mounts
297 userspace id mapped. This will come in handy when working with idmapped mounts.
540 Idmappings on idmapped mounts
605 But the usecases mentioned above and more can be handled by idmapped mounts.
607 different mounts. This is achieved by marking the mounts with a user namespace
612 Idmapped mounts make it possible to change ownership in a temporary and
617 Filesystems that support idmapped mounts don't have any real reason to support
623 However, it is perfectly possible to combine idmapped mounts with filesystems
718 of idmapped mounts.
811 /* Map the userspace id down into a kernel id in the mounts's idmapping. */
847 /* Map the userspace id down into a kernel id in the mounts's idmapping. */
862 We've seen above how idmapped mounts can be used to translate between
871 As we've seen above idmapped mounts provide a solution to this by remapping the
874 Aside from containerized workloads, idmapped mounts have the advantage that
888 Idmapped mounts allow to solve this problem. A user can create an idmapped
946 /* Map the userspace id down into a kernel id in the mounts's idmapping. */