Re: [PATCH] prctl: Allow local CAP_SYS_ADMIN changing exe_file

2017-05-12 Thread Kirill Tkhai
On 12.05.2017 17:56, Eric W. Biederman wrote: > Kirill Tkhai writes: > >> During checkpointing and restore of userspace tasks >> we bumped into the situation, that it's not possible >> to restore the tasks, which user namespace does not >> have uid 0 or gid 0 mapped. >> >> People create user name

Re: [PATCH] prctl: Allow local CAP_SYS_ADMIN changing exe_file

2017-05-12 Thread Eric W. Biederman
Kirill Tkhai writes: > During checkpointing and restore of userspace tasks > we bumped into the situation, that it's not possible > to restore the tasks, which user namespace does not > have uid 0 or gid 0 mapped. > > People create user namespace mappings like they want, > and there is no a limit

Re: [PATCH] prctl: Allow local CAP_SYS_ADMIN changing exe_file

2017-05-12 Thread Cyrill Gorcunov
On Fri, May 12, 2017 at 05:33:36PM +0300, Kirill Tkhai wrote: > During checkpointing and restore of userspace tasks > we bumped into the situation, that it's not possible > to restore the tasks, which user namespace does not > have uid 0 or gid 0 mapped. > > People create user namespace mappings l

[PATCH] prctl: Allow local CAP_SYS_ADMIN changing exe_file

2017-05-12 Thread Kirill Tkhai
During checkpointing and restore of userspace tasks we bumped into the situation, that it's not possible to restore the tasks, which user namespace does not have uid 0 or gid 0 mapped. People create user namespace mappings like they want, and there is no a limitation on obligatory uid and gid "mus