Lines Matching +full:non +full:- +full:overlapping

1 .. SPDX-License-Identifier: GPL-2.0
12 ------------
32  u22 -> k10000
33  u23 -> k10001
34  u24 -> k10002
36 From a mathematical viewpoint ``U`` and ``K`` are well-ordered sets and an
38 order isomorphic. In fact, ``U`` and ``K`` are always well-ordered subsets of
45  k10000 -> u22
46  k10001 -> u23
47  k10002 -> u24
81 ``(uid_t)-1`` or overflowgid ``(gid_t)-1`` to userspace.
88 - If we want to map from left to right::
91    id - u + k = n
93 - If we want to map from right to left::
96    id - k + u = n
111  id     - k      + u  = n
112  k21000 - k20000 + u0 = u1000
119  id    - u    + k      = n
120  u1100 - u500 + k30000 = k30600
123 -------------
128  userspace-id:kernel-id:range
168 Other user namespaces usually have non-identity idmappings such as::
180 - If a filesystem were to be mounted in the initial user namespaces (as most
186 - If a filesystem were to be mounted with an idmapping of ``u0:k10000:r10000``
191 ----------------------
329 -------------------------------------------
380     - caller's idmapping (usually taken from ``current_user_ns()``)
381     - filesystem's idmapping (``sb->s_user_ns``)
382     - mount's idmapping (``mnt_idmap(vfsmnt)``)
433     from_kuid(u0:k20000:r10000, k11000) = u-1
441 mounted with non-initial idmappings this is a general problem as we can see in
471 filesystems and not very flexible. But this is a use-case that is pretty
484     from_kuid(u0:k10000:r10000, k1000) = u-1
505     from_kuid(u0:k10000:r10000, k1000) = u-1
531     from_kuid(u0:k10000:r10000, k21000) = u-1
553 -----------------------------
559 each other, an administrator may often use different non-overlapping idmappings
566 An administrator wanting to provide easy read-write access to the following set
662  uid_t <--> kuid_t <--> vfsuid_t
663  gid_t <--> kgid_t <--> vfsgid_t
704 - ``i_uid_into_vfsuid()`` and ``i_gid_into_vfsgid()``
715 - ``mapped_fsuid()`` and ``mapped_fsgid()``
727 - ``vfsuid_into_kuid()`` and ``vfsgid_into_kgid()``
807 When the caller is using a non-initial idmapping the common case is to attach
942 idmappings when either the caller, the filesystem or both uses a non-initial
944 a non-initial idmapping. This mostly happens in the context of containerized
946 mounted with the initial idmapping and filesystems mounted with non-initial
956 and files on a per-mount basis.