Lines Matching refs: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 usable 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
165 which is an identity idmapping over the full range of ids available on this
324 Since userspace ids have type ``uid_t`` and ``gid_t`` and kernel ids have type
349 filesystem ids. These are just regular ``uid_t`` and ``gid_t`` userspace ids
351 are called "filesystem ids". They are usually identical to the uid and gid of
357 1. Map the caller's userspace ids down into kernel ids in the caller's
359    (To be precise, the kernel will simply look at the kernel ids stashed in the
362 2. Verify that the caller's kernel ids can be mapped up to userspace ids in the
400 1. Map the caller's userspace ids into kernel ids in the caller's idmapping::
404 2. Verify that the caller's kernel ids can be mapped to userspace ids in the
425 1. Map the caller's userspace ids down into kernel ids in the caller's
430 2. Verify that the caller's kernel ids can be mapped up to userspace ids in the
436 successfully mapped down into kernel ids in the caller's idmapping the kernel
437 ids could not be mapped up according to the filesystem's idmapping. So the
453 1. Map the caller's userspace ids down into kernel ids in the caller's
458 2. Verify that the caller's kernel ids can be mapped up to userspace ids in the
476 kernel ids map up into valid userspace ids in the caller's idmapping
478 1. Map raw userspace ids down to kernel ids in the filesystem's idmapping::
482 2. Map kernel ids up to userspace ids in the caller's idmapping::
592 different login userspace ids. Most users will have ``u1000`` as the login id
694 Similar to how we prefix all userspace ids in this document with ``u`` and all
695 kernel ids with ``k`` we will prefix all VFS ids with ``v``. So a mount
706   The ``i_*id_into_vfs*id()`` functions translate filesystem's kernel ids into
707   VFS ids in the mount's idmapping::
717   The ``mapped_fs*id()`` functions translate the caller's kernel ids into
718   kernel ids in the filesystem's idmapping. This translation is achieved by
719   remapping the caller's VFS ids using the mount's idmapping::
810 1. Map the caller's userspace ids into kernel ids in the caller's idmapping::
824 2. Verify that the caller's kernel ids can be mapped to userspace ids in the
843 1. Map the caller's userspace ids into kernel ids in the caller's idmapping::
857 2. Verify that the caller's kernel ids can be mapped to userspace ids in the
947 idmappings, access to the filesystem isn't working because the kernel ids can't
983 1. Map the caller's userspace ids into kernel ids in the caller's idmapping::
997 2. Verify that the caller's filesystem ids can be mapped to userspace ids in the