Lines Matching full:into
14 An idmapping is essentially a translation of a range of ids into another or the
37 idmapping is an order isomorphism from ``U`` into ``K``. So ``U`` and ``K`` are
50 dealing with subsets we can embedd idmappings into each other, i.e. we can
126 of userspace ids into a range of kernel ids::
173 immediately translated into a kernel id according to the idmapping associated
211 then translate ``k11000`` into a userspace id in the second idmapping using the
214 /* Map the kernel id up into a userspace id in the second idmapping. */
220 /* Map the userspace id down into a kernel id in the second idmapping. */
223 /* Map the kernel id up into a userspace id in the first idmapping. */
232 into a kernel id according to the idmapping associated with the filesystem.
261 kernel id in the first idmapping into a kernel id in the second idmapping we
264 1. Map the kernel id up into a userspace id in the first idmapping::
266 /* Map the kernel id up into a userspace id in the first idmapping. */
269 2. Map the userspace id down into a kernel id in the second idmapping::
271 /* Map the userspace id down into a kernel id in the second idmapping. */
285 1. Map the kernel id up into a userspace id in the second idmapping::
287 /* Map the kernel id up into a userspace id in the second idmapping. */
290 2. Map the userspace id down into a kernel id in the first idmapping::
292 /* Map the userspace id down into a kernel id in the first idmapping. */
307 /* Map the userspace id down into a kernel id in the first idmapping. */
310 /* INVALID: Map the kernel id down into a kernel id in the second idmapping. */
316 /* Map the kernel id up into a userspace id in the first idmapping. */
319 /* INVALID: Map the userspace id up into a userspace id in the second idmapping. */
330 /* Map the userspace id down into a kernel id. */
333 /* Map the kernel id up into a userspace id. */
336 We will take an abbreviated look into how idmappings figure into creating
338 VFS has already completed path lookup right before it calls into the filesystem
352 1. Map the caller's userspace ids down into kernel ids in the caller's
361 the kernel id back up into a userspace id when writing to disk.
368 kernel maps the caller's userspace id down into a kernel id according to the
388 1. Map the caller's userspace ids into kernel ids in the caller's idmapping::
413 1. Map the caller's userspace ids down into kernel ids in the caller's
424 successfully mapped down into kernel ids in the caller's idmapping the kernel
441 1. Map the caller's userspace ids down into kernel ids in the caller's
464 kernel ids map up into valid userspace ids in the caller's idmapping
486 1. Map the userspace id on disk down into a kernel id in the filesystem's
491 2. Map the kernel id up into a userspace id in the caller's idmapping::
512 1. Map the userspace id on disk down into a kernel id in the filesystem's
517 2. Map the kernel id up into a userspace id in the caller's idmapping::
531 1. Map the userspace id on disk down into a kernel id in the filesystem's
536 2. Map the kernel id up into a userspace id in the caller's idmapping::
565 files below it can be crossmapped from the filesystem's into the container's
635 The ``i_*id_into_mnt()`` functions translate filesystem's kernel ids into
638 /* Map the filesystem's kernel id up into a userspace id in the filesystem's idmapping. */
646 The ``mapped_fs*id()`` functions translate the caller's kernel ids into
650 /* Map the caller's kernel id up into a userspace id in the mount's idmapping. */
653 /* Map the mount's userspace id down into a kernel id in the filesystem's idmapping. */
673 into a kernel id in the mount's idmapping::
676 /* Map the filesystem's kernel id up into a userspace id. */
683 kernel id in the mount's idmapping into a userspace id in the caller's
698 first call ``mapped_fs*id()`` thereby translating the caller's kernel id into
702 /* Map the caller's kernel id up into a userspace id in the mount's idmapping. */
705 /* Map the mount's userspace id down into a kernel id in the filesystem's idmapping. */
708 When finally writing to disk the kernel will then map ``k21000`` up into a
733 1. Map the caller's userspace ids into kernel ids in the caller's idmapping::
737 2. Translate the caller's kernel id into a kernel id in the filesystem's
741 /* Map the kernel id up into a userspace id in the mount's idmapping. */
744 /* Map the userspace id down into a kernel id in the filesystem's idmapping. */
766 1. Map the caller's userspace ids into kernel ids in the caller's idmapping::
770 2. Translate the caller's kernel id into a kernel id in the filesystem's
774 /* Map the kernel id up into a userspace id in the mount's idmapping. */
777 /* Map the userspace id down into a kernel id in the filesystem's idmapping. */
800 1. Map the userspace id on disk down into a kernel id in the filesystem's
805 2. Translate the kernel id into a kernel id in the mount's idmapping::
808 /* Map the kernel id up into a userspace id in the filesystem's idmapping. */
811 /* Map the userspace id down into a kernel id in the mounts's idmapping. */
814 3. Map the kernel id up into a userspace id in the caller's idmapping::
819 idmapping. With the idmapped mount in place it now can be crossmapped into the
836 1. Map the userspace id on disk down into a kernel id in the filesystem's
841 2. Translate the kernel id into a kernel id in the mount's idmapping::
844 /* Map the kernel id up into a userspace id in the filesystem's idmapping. */
847 /* Map the userspace id down into a kernel id in the mounts's idmapping. */
850 3. Map the kernel id up into a userspace id in the caller's idmapping::
855 idmapping. With the idmapped mount in place it now can be crossmapped into the
904 1. Map the caller's userspace ids into kernel ids in the caller's idmapping::
908 2. Translate the caller's kernel id into a kernel id in the filesystem's
912 /* Map the kernel id up into a userspace id in the mount's idmapping. */
915 /* Map the userspace id down into a kernel id in the filesystem's idmapping. */
935 1. Map the userspace id on disk down into a kernel id in the filesystem's
940 2. Translate the kernel id into a kernel id in the mount's idmapping::
943 /* Map the kernel id up into a userspace id in the filesystem's idmapping. */
946 /* Map the userspace id down into a kernel id in the mounts's idmapping. */
949 3. Map the kernel id up into a userspace id in the caller's idmapping::