Re: [PATCH 2/2] pidns: Expose task pid_ns_for_children to userspace

2017-01-30 Thread Kirill Tkhai
ping On 14.01.2017 17:15, Kirill Tkhai wrote: > For correct checkpointing/restoring of a task from userspace > it's need to know the task's pid_ns_for_children. Currently, > there is no a sane way to do that (the only possible trick > is to force the task create a new child and to analize the > ch

Re: [PATCH 2/2] pidns: Expose task pid_ns_for_children to userspace

2017-01-24 Thread Kirill Tkhai
On 24.01.2017 00:49, Alban Crequy wrote: > On 14 January 2017 at 15:15, Kirill Tkhai wrote: >> For correct checkpointing/restoring of a task from userspace >> it's need to know the task's pid_ns_for_children. Currently, >> there is no a sane way to do that (the only possible trick >> is to force t

Re: [PATCH 2/2] pidns: Expose task pid_ns_for_children to userspace

2017-01-23 Thread Alban Crequy
On 14 January 2017 at 15:15, Kirill Tkhai wrote: > For correct checkpointing/restoring of a task from userspace > it's need to know the task's pid_ns_for_children. Currently, > there is no a sane way to do that (the only possible trick > is to force the task create a new child and to analize the >

Re: [PATCH 2/2] pidns: Expose task pid_ns_for_children to userspace

2017-01-17 Thread Andrei Vagin
On Sat, Jan 14, 2017 at 05:15:04PM +0300, Kirill Tkhai wrote: > For correct checkpointing/restoring of a task from userspace > it's need to know the task's pid_ns_for_children. Currently, > there is no a sane way to do that (the only possible trick > is to force the task create a new child and to a

[PATCH 2/2] pidns: Expose task pid_ns_for_children to userspace

2017-01-14 Thread Kirill Tkhai
For correct checkpointing/restoring of a task from userspace it's need to know the task's pid_ns_for_children. Currently, there is no a sane way to do that (the only possible trick is to force the task create a new child and to analize the child's /proc/[pid]/ns/pid link, that is performance-stupid