On 31.03.2017 18:06, Kees Cook wrote:
> On Fri, Mar 31, 2017 at 2:45 AM, Kirill Tkhai wrote:
>> On 31.03.2017 04:04, Andrei Vagin wrote:
>>> On Thu, Mar 30, 2017 at 03:05:20PM -0700, Andrew Morton wrote:
On Thu, 30 Mar 2017 13:27:59 +0300 Kirill Tkhai
wrote:
> pid_ns_for_child
On Fri, Mar 31, 2017 at 2:45 AM, Kirill Tkhai wrote:
> On 31.03.2017 04:04, Andrei Vagin wrote:
>> On Thu, Mar 30, 2017 at 03:05:20PM -0700, Andrew Morton wrote:
>>> On Thu, 30 Mar 2017 13:27:59 +0300 Kirill Tkhai
>>> wrote:
>>>
pid_ns_for_children set by a task is known only to the task it
On 31.03.2017 04:04, Andrei Vagin wrote:
> On Thu, Mar 30, 2017 at 03:05:20PM -0700, Andrew Morton wrote:
>> On Thu, 30 Mar 2017 13:27:59 +0300 Kirill Tkhai wrote:
>>
>>> pid_ns_for_children set by a task is known only to the task itself,
>>> and it's impossible to identify it from outside.
>>>
>>
On Thu, Mar 30, 2017 at 03:05:20PM -0700, Andrew Morton wrote:
> On Thu, 30 Mar 2017 13:27:59 +0300 Kirill Tkhai wrote:
>
> > pid_ns_for_children set by a task is known only to the task itself,
> > and it's impossible to identify it from outside.
> >
> > It's a big problem for checkpoint/restore
On Thu, 30 Mar 2017 13:27:59 +0300 Kirill Tkhai wrote:
> pid_ns_for_children set by a task is known only to the task itself,
> and it's impossible to identify it from outside.
>
> It's a big problem for checkpoint/restore software like CRIU,
> because it can't correctly handle tasks, that do set
pid_ns_for_children set by a task is known only to the task itself,
and it's impossible to identify it from outside.
It's a big problem for checkpoint/restore software like CRIU,
because it can't correctly handle tasks, that do setns(CLONE_NEWPID)
in proccess of their work.
This patch solves the
6 matches
Mail list logo