Re: [PATCH v2] /proc/pid/status: show all sets of pid according to ns
From: Pavel Emelyanov
Date: Thu May 29 2014 - 06:37:35 EST
On 05/29/2014 02:19 PM, Richard Weinberger wrote:
> Am 29.05.2014 12:02, schrieb Pavel Emelyanov:
>>>> We need to know what pid namespaces a task lives in and how pid, sid and
>>>> pgid look in all of them. A short example with pids only
>>>
>>> So use case is to checkpoint/restore nested containers? :)
>>
>> Yes, but there's one more scenario. AFAIK some applications create pid namespaces
>> themselves, without starting what is typically called "a container" :) And when
>> such an applications are run inside, well ... "more real" container (e.g. using
>> openvz, lxc or docker tools) we face this issue.
>
> Do you know such an application?
There were a couple of them reported on the criu mailing list, but I didn't
track those :(
> I'm a aware of systemd which uses CLONE_NEWNET/NS to implement security features.
Yup, this is its typical behavior.
> We could add a directory like /proc/<pidX>/ns/proc/ which would contain everything
> from /proc/<pidX inside the namespace>/.
But how would it help to find out which $pid directories correspond to which
to properly collect the pid mappings?
> This needs definitely more discussion and must not solved by ad-hoc solutions.
Absolutely.
Thanks,
Pavel
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/