Aleksa Sarai 482e56379a configs: make id mappings int64 to better handle 32-bit ...

Using ints for all of our mapping structures means that a 32-bit binary
errors out when trying to parse /proc/self/*id_map:

  failed to cache mappings for userns: failed to parse uid_map of userns /proc/1/ns/user:
  parsing id map failed: invalid format in line "         0          0 4294967295": integer overflow on token 4294967295

This issue was unearthed by commit 1912d5988b ("*: actually support
joining a userns with a new container") but the underlying issue has
been present since the docker/libcontainer days.

In theory, switching to uint32 (to match the spec) instead of int64
would also work, but keeping everything signed seems much less
error-prone. It's also important to note that a mapping might be too
large for an int on 32-bit, so we detect this during the mapping.

Signed-off-by: Aleksa Sarai <cyphar@cyphar.com>

2023-12-14 12:14:32 +11:00

..

example.go

runc: do not set inheritable capabilities

2022-05-12 08:14:50 +10:00

spec_linux_test.go

specconv: temporarily allow userns path and mapping if they match

2023-12-10 20:49:43 +11:00

spec_linux.go

configs: make id mappings int64 to better handle 32-bit

2023-12-14 12:14:32 +11:00