Lines Matching full:ids
14 An idmapping is essentially a translation of a range of ids into another or the
15 same range of ids. The notational convention for idmappings that is widely used
22 indicates the range of the idmapping, i.e. how many ids are mapped. From now
23 on, we will always prefix ids with ``u`` or ``k`` to make it clear whether
39 the set of all possible ids useable on a given system.
80 third idmapping. The kernel will report unmapped ids as the overflowuid
126 of userspace ids into a range of kernel ids::
136 The kernel is mostly concerned with kernel ids. They are used when performing
145 For the rest of this document we will prefix all userspace ids with ``u`` and
146 all kernel ids with ``k``. Ranges of idmappings will be prefixed with ``r``. So
164 which is an identity idmapping over the full range of ids available on this
344 filesystem ids. These are just regular ``uid_t`` and ``gid_t`` userspace ids
346 are called "filesystem ids". They are usually identical to the uid and gid of
352 1. Map the caller's userspace ids down into kernel ids in the caller's
354 (To be precise, the kernel will simply look at the kernel ids stashed in the
357 2. Verify that the caller's kernel ids can be mapped up to userspace ids in the
388 1. Map the caller's userspace ids into kernel ids in the caller's idmapping::
392 2. Verify that the caller's kernel ids can be mapped to userspace ids in the
413 1. Map the caller's userspace ids down into kernel ids in the caller's
418 2. Verify that the caller's kernel ids can be mapped up to userspace ids in the
424 successfully mapped down into kernel ids in the caller's idmapping the kernel
425 ids could not be mapped up according to the filesystem's idmapping. So the
441 1. Map the caller's userspace ids down into kernel ids in the caller's
446 2. Verify that the caller's kernel ids can be mapped up to userspace ids in the
464 kernel ids map up into valid userspace ids in the caller's idmapping
466 1. Map raw userspace ids down to kernel ids in the filesystem's idmapping::
470 2. Map kernel ids up to userspace ids in the caller's idmapping::
580 different login userspace ids. Most users will have ``u1000`` as the login id
635 The ``i_*id_into_mnt()`` functions translate filesystem's kernel ids into
636 kernel ids in the mount's idmapping::
646 The ``mapped_fs*id()`` functions translate the caller's kernel ids into
647 kernel ids in the filesystem's idmapping. This translation is achieved by
648 remapping the caller's kernel ids using the mount's idmapping::
733 1. Map the caller's userspace ids into kernel ids in the caller's idmapping::
747 2. Verify that the caller's kernel ids can be mapped to userspace ids in the
766 1. Map the caller's userspace ids into kernel ids in the caller's idmapping::
780 2. Verify that the caller's kernel ids can be mapped to userspace ids in the
868 idmappings, access to the filesystem isn't working because the kernel ids can't
904 1. Map the caller's userspace ids into kernel ids in the caller's idmapping::
918 2. Verify that the caller's kernel ids can be mapped to userspace ids in the