Lines Matching full:translate

42 that make it easier to understand how we can translate between idmappings. For
51 sensibly translate between different idmappings. For example, assume we've been
75 we would fail to translate as the sets aren't order isomorphic over the full
193 We've already seen briefly that it is possible to translate between different
212 then translate ``k11000`` into a userspace id in the second idmapping using the
252 It is possible to translate a kernel id from one idmapping to another one via
261 and we are given ``k11000`` in the first idmapping. In order to translate this
275 As you can see we used the userspace idmapset in both idmappings to translate
621 is then used to translate from the caller's idmapping to the filesystem's
701 Idmapping functions were added that translate between idmappings. They make use
706   The ``i_*id_into_vfs*id()`` functions translate filesystem's kernel ids into
717   The ``mapped_fs*id()`` functions translate the caller's kernel ids into
814 2. Translate the caller's VFS id into a kernel id in the filesystem's
847 2. Translate the caller's VFS id into a kernel id in the filesystem's
882 2. Translate the kernel id into a VFS id in the mount's idmapping::
919 2. Translate the kernel id into a VFS id in the mount's idmapping::
941 We've seen above how idmapped mounts can be used to translate between
987 2. Translate the caller's VFS id into a kernel id in the filesystem's
1019 2. Translate the kernel id into a VFS id in the mount's idmapping::