[CRIU] How can I get "real pid" in pid namespace?

[Qiang Huang]

On 2013/7/1 15:19, Chanho Park wrote:
>> I think your need is "Other processes can identify the process from pid",
>> and "convert vpid to pid" is one solution you figured out, right?
>>
>> So here I offer another solution to satisfy the needs, since we have
>> this function in kernel:
> 
> I know we can get vpid and pid and pidns and any other things in the kernel
> level.
> I mean, "Does it possible in the user level?"
> To export vpid and pidns, we should implement more things in the kernel
> layer.

Yes, I think I get it now :)

> 
> I think it looks like blue pill and red pill in the Matrix movie.
> To exit from the container, we should eat the red pill :)
> 
> Return to CRIU, if we don't use pid namespace, dumped pid will be not
> changed.
> If a machine already use the pid, we can't restore the state.
> To avoid this problem, we should use the namespace features.
> However, if we use the pid namespace, we can't support the behavior which
> communicates pid information out of the container.

I think it's a container issue, is this kind of leak? Communicate with
some process with pid information, shouldn't they be in the same pidns?

Maybe you can describe your problem more specific and cc LXC mail list.

> 
> Best Regards,
> Chanho Park
> 
> 
>