Lines Matching full:would

66 idmapping would map ``u1000`` down to ``21000``. The third idmapping would map
75 we would fail to translate as the sets aren't order isomorphic over the full
143 how userspace would specify them.
181   simply the identity idmapping. This would mean id ``u1000`` read from disk
182   would be mapped to id ``k1000``. So an inode's ``i_uid`` and ``i_gid`` field
183   would contain ``k1000``.
186   then ``u1000`` read from disk would be mapped to ``k11000``. So an inode's
187   ``i_uid`` and ``i_gid`` would contain ``k11000``.
240 according to the filesystem's idmapping as this would give the wrong owner if
245 ``u3000:k20000:r10000`` then ``k21000`` would map back up to ``u4000``.
246 Consequently the user would see that this file is owned by ``u4000``.
277 This allows us to answer the question what kernel id we would need to use to
521 Note how in the last two examples things would be simple if the caller would be
523 idmapping it would be trivial. So we only consider a filesystem with an
568 This would still leave ``dir`` rather useless to the second container. In fact,
569 ``dir`` and all files below it would continue to appear owned by the overflowid
583 directory case this change in ownership would even need to happen everytime the
588 inside user namespaces. But this would also change ownership globally and the
592 impossible because it would mean that all users currently accessing the
663 would usually simply use the crossmapping algorithm and map the filesystem's
687 kernel would now apply the crossmapping, verifying that ``k11000`` can be
885 depending on what ownership they would prefer to end up on the portable storage