On Wed, Feb 22, 2017 at 5:29 PM, Eric W. Biederman
wrote:
> Aleksa Sarai writes:
>
>>> The only known user of this prctl systemd
>>> forks all children after the prctl. So no userspace regressions will
>>> occur.
>>
>> Note that runC and containerd (and thus Docker) as well as cri-o use the
>>
The only known user of this prctl systemd
forks all children after the prctl. So no userspace regressions will
occur.
Note that runC and containerd (and thus Docker) as well as cri-o use the prctl
as well -- to be able to collect exit codes from a non-child process (namely to
collect the exit c
Aleksa Sarai writes:
>> The only known user of this prctl systemd
>> forks all children after the prctl. So no userspace regressions will
>> occur.
>
> Note that runC and containerd (and thus Docker) as well as cri-o use the prctl
> as well -- to be able to collect exit codes from a non-child pr
Linus,
Please pull the for-linus branch from the git tree:
git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git
for-linus
HEAD: ace0c791e6c3cf5ef37cad2df69f0d90ccc40ffb proc/sysctl: Don't grab
i_lock under sysctl_lock.
This pull request is coming a few days into th
The only known user of this prctl systemd
forks all children after the prctl. So no userspace regressions will
occur.
Note that runC and containerd (and thus Docker) as well as cri-o use the
prctl as well -- to be able to collect exit codes from a non-child
process (namely to collect the exit
5 matches
Mail list logo
