From: Andrew Morton <akpm@linux-foundation.org>
To: Chen Hanxiao <chenhanxiao@cn.fujitsu.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
<containers@lists.linux-foundation.org>,
<linux-kernel@vger.kernel.org>, <linux-doc@vger.kernel.org>,
Serge Hallyn <serge.hallyn@ubuntu.com>,
Jonathan Corbet <corbet@lwn.net>,
Gui Jianfeng <guijianfeng@cn.fujitsu.com>,
Nathan Scott <nathans@redhat.com>
Subject: Re: [PATCH v10 1/2] /proc/PID/status: show all sets of pid according to ns
Date: Mon, 23 Feb 2015 13:00:09 -0800 [thread overview]
Message-ID: <20150223130009.2c9c3f47d6d1dc183a5b2916@linux-foundation.org> (raw)
In-Reply-To: <1423219550-4385-2-git-send-email-chenhanxiao@cn.fujitsu.com>
On Fri, 6 Feb 2015 18:45:49 +0800 Chen Hanxiao <chenhanxiao@cn.fujitsu.com> 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
>
> ...
>
> --- a/fs/proc/array.c
> +++ b/fs/proc/array.c
> @@ -208,6 +208,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');
> }
Is there any point in including this code if CONFIG_USER_NS=n?
next prev parent reply other threads:[~2015-02-23 21:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-06 10:45 [PATCH v10 0/2] ns, procfs: pid conversion between ns Chen Hanxiao
2015-02-06 10:45 ` [PATCH v10 1/2] /proc/PID/status: show all sets of pid according to ns Chen Hanxiao
2015-02-23 21:00 ` Andrew Morton [this message]
2015-02-23 21:20 ` Serge E. Hallyn
2015-02-06 10:45 ` [PATCH v10 2/2] docs: add missing and new /proc/PID/status file entries, fix typos Chen Hanxiao
2015-02-23 21:01 ` Andrew Morton
2015-02-27 10:05 ` Chen, Hanxiao
2015-02-11 5:51 ` [PATCH v10 0/2] ns, procfs: pid conversion between ns Chen, Hanxiao
2015-02-12 1:35 ` Chen, Hanxiao
2015-02-16 1:58 ` "Gui, Jianfeng/归 剑峰"
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150223130009.2c9c3f47d6d1dc183a5b2916@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=chenhanxiao@cn.fujitsu.com \
--cc=containers@lists.linux-foundation.org \
--cc=corbet@lwn.net \
--cc=ebiederm@xmission.com \
--cc=guijianfeng@cn.fujitsu.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathans@redhat.com \
--cc=serge.hallyn@ubuntu.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®