From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934440AbaE2JV0 (ORCPT ); Thu, 29 May 2014 05:21:26 -0400 Received: from a.ns.miles-group.at ([95.130.255.143]:47834 "EHLO radon.swed.at" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934228AbaE2JVY (ORCPT ); Thu, 29 May 2014 05:21:24 -0400 Message-ID: <5386FC0C.9000307@nod.at> Date: Thu, 29 May 2014 11:21:16 +0200 From: Richard Weinberger User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: Pavel Emelyanov , Vasily Kulikov CC: containers@lists.linux-foundation.org, Serge Hallyn , linux-kernel@vger.kernel.org, Oleg Nesterov , David Howells , "Eric W. Biederman" , Andrew Morton , Al Viro Subject: Re: [PATCH v2] /proc/pid/status: show all sets of pid according to ns References: <1401272683-1659-1-git-send-email-chenhanxiao@cn.fujitsu.com> <5385DA19.2060008@parallels.com> <20140528182824.GA5057@cachalot> <53863889.9080509@parallels.com> <20140529055954.GA10354@cachalot> <5386F8EA.8050501@parallels.com> In-Reply-To: <5386F8EA.8050501@parallels.com> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Am 29.05.2014 11:07, schrieb Pavel Emelyanov: > On 05/29/2014 09:59 AM, Vasily Kulikov wrote: >> On Wed, May 28, 2014 at 23:27 +0400, Pavel Emelyanov wrote: >>> On 05/28/2014 10:28 PM, Vasily Kulikov wrote: >>>> On Wed, May 28, 2014 at 16:44 +0400, Pavel Emelyanov wrote: >>>> It will be simplier >>>> to parse the file -- if 'ns_ids' file contains some ID then this ID for >>>> every ns can be obtained regardless of the specific ID name (SID, PID, >>>> PGID, etc.). >>> >>> True, but given a task PID how to determine which pid namespaces it lives in >>> to get the idea of how PIDs map to each other? Maybe we need some explicit >>> API for converting (ID, NS1, NS2) into (ID)? >> >> AFAIU the idea of the patch is to add a new debugging information which >> can be trivially obtained via 'cat /proc/...': > > I agree, but this ability will be very useful by checkpoint-restore project > too and I'd really appreciate if the API we have for that would be scalable > enough. Per-task proc file works for me, but how about sid-s and pgid-s? What kind of information does CRIU need? Thanks, //richard