Lines Matching full:second

62 what id ``k11000`` corresponds to in the second or third idmapping. The
65 either the second idmapping mapping or third idmapping mapping. The second
77 the full range of the second idmapping.). Neither the second or third idmapping
79 an id mapped. We can simply say that ``u1000`` is unmapped in the second and
114 Now assume we are given the id ``u1100`` in the upper idmapset of the second
116 of the second idmapping. This means we're mapping down in the second
212 then translate ``k11000`` into a userspace id in the second idmapping using the
213 kernel idmapset of the second idmapping::
215  /* Map the kernel id up into a userspace id in the second idmapping. */
221  /* Map the userspace id down into a kernel id in the second idmapping. */
262 kernel id in the first idmapping into a kernel id in the second idmapping we
270 2. Map the userspace id down into a kernel id in the second idmapping::
272     /* Map the userspace id down into a kernel id in the second idmapping. */
286 1. Map the kernel id up into a userspace id in the second idmapping::
288     /* Map the kernel id up into a userspace id in the second idmapping. */
311  /* INVALID: Map the kernel id down into a kernel id in the second idmapping. */
320  /* INVALID: Map the userspace id up into a userspace id in the second idmapping. */
365 The second step is important as regular filesystem will ultimately need to map
367 So with the second step the kernel guarantees that a valid userspace id can be
407    For this second step the kernel will call the function
474 Second, the caller will usually not be able to create any files or access
585 This would still leave ``dir`` rather useless to the second container. In fact,
587 for the second container.