Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752760AbbBWQ5E (ORCPT ); Mon, 23 Feb 2015 11:57:04 -0500 Received: from h2.hallyn.com ([78.46.35.8]:56973 "EHLO h2.hallyn.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752072AbbBWQ5C (ORCPT ); Mon, 23 Feb 2015 11:57:02 -0500 Date: Mon, 23 Feb 2015 10:56:59 -0600 From: "Serge E. Hallyn" To: Chen Hanxiao Cc: "Eric W. Biederman" , Andrew Morton , Jonathan Corbet , containers@lists.linux-foundation.org, Serge Hallyn , linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, Nathan Scott Subject: Re: [resend][PATCH v10 1/2] /proc/PID/status: show all sets of pid according to ns Message-ID: <20150223165659.GD32181@mail.hallyn.com> References: <1424605685-5081-1-git-send-email-chenhanxiao@cn.fujitsu.com> <1424605685-5081-2-git-send-email-chenhanxiao@cn.fujitsu.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1424605685-5081-2-git-send-email-chenhanxiao@cn.fujitsu.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3232 Lines: 88 On Sun, Feb 22, 2015 at 07:48:04PM +0800, Chen Hanxiao wrote: > If some issues occurred inside a container guest, host user > could not know which process is in trouble just by guest pid: > the users of container guest only knew the pid inside containers. > This will bring obstacle for trouble shooting. > > This patch adds four fields: NStgid, NSpid, NSpgid and NSsid: > a) In init_pid_ns, nothing changed; > > b) In one pidns, will tell the pid inside containers: > NStgid: 21776 5 1 > NSpid: 21776 5 1 > NSpgid: 21776 5 1 > NSsid: 21729 1 0 > ** Process id is 21776 in level 0, 5 in level 1, 1 in level 2. > > c) If pidns is nested, it depends on which pidns are you in. > NStgid: 5 1 > NSpid: 5 1 > NSpgid: 5 1 > NSsid: 1 0 > ** Views from level 1 So obviously (since I acked it) I see no problems with this patch or the api, but it occurs to me that you have not cc:d linux-api? Since a procfile addition is something we're stuck with for eternity, it seems worth it. If we get an ack from there, then i'd say email to Linus directly. Putting this through -mm doesn't really seem necessary given its nature. > Acked-by: Serge Hallyn > Acked-by: "Eric W. Biederman" > > Tested-by: Serge Hallyn > Tested-by: Nathan Scott > > Signed-off-by: Chen Hanxiao > --- > v10: remove trailing space of pid numbers > rebased on 3.19 > v9: rebased on 3.19-rc1 > No change from v4-v8 > v3: add another two fielsd: NSpgid and NSsid. > v2: add two new fields: NStgid and NSpid. > keep fields of Tgid and Pid unchanged for back compatibility. > > fs/proc/array.c | 16 ++++++++++++++++ > 1 file changed, 16 insertions(+) > > diff --git a/fs/proc/array.c b/fs/proc/array.c > index 1295a00..d79bad9 100644 > --- a/fs/proc/array.c > +++ b/fs/proc/array.c > @@ -188,6 +188,22 @@ static inline void task_state(struct seq_file *m, struct pid_namespace *ns, > from_kgid_munged(user_ns, GROUP_AT(group_info, g))); > put_cred(cred); > > + seq_puts(m, "\nNStgid:"); > + for (g = ns->level; g <= pid->level; g++) > + seq_printf(m, "\t%d", > + task_tgid_nr_ns(p, pid->numbers[g].ns)); > + seq_puts(m, "\nNSpid:"); > + for (g = ns->level; g <= pid->level; g++) > + seq_printf(m, "\t%d", > + task_pid_nr_ns(p, pid->numbers[g].ns)); > + seq_puts(m, "\nNSpgid:"); > + for (g = ns->level; g <= pid->level; g++) > + seq_printf(m, "\t%d", > + task_pgrp_nr_ns(p, pid->numbers[g].ns)); > + seq_puts(m, "\nNSsid:"); > + for (g = ns->level; g <= pid->level; g++) > + seq_printf(m, "\t%d", > + task_session_nr_ns(p, pid->numbers[g].ns)); > seq_putc(m, '\n'); > } > > -- > 2.1.0 > > _______________________________________________ > Containers mailing list > Containers@lists.linux-foundation.org > https://lists.linuxfoundation.org/mailman/listinfo/containers -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/