From: ebiederm@xmission.com (Eric W. Biederman)
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: Konstantin Khlebnikov <khlebnikov@yandex-team.ru>,
Nagarathnam Muthusamy <nagarathnam.muthusamy@oracle.com>,
linux-api@vger.kernel.org, linux-kernel@vger.kernel.org,
Jann Horn <jannh@google.com>,
Serge Hallyn <serge.hallyn@ubuntu.com>,
Oleg Nesterov <oleg@redhat.com>,
Andy Lutomirski <luto@amacapital.net>,
Prakash Sangappa <prakash.sangappa@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH RFC v5] pidns: introduce syscall translate_pid
Date: Thu, 31 May 2018 13:02:33 -0500 [thread overview]
Message-ID: <871sdrem9y.fsf@xmission.com> (raw)
In-Reply-To: <71d8d32b-0f59-d418-0ee4-fcc7782646ae@gmail.com> (Michael Kerrisk's message of "Fri, 27 Apr 2018 14:15:01 +0200")
"Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com> writes:
> On 04/05/2018 09:02 AM, Konstantin Khlebnikov wrote:
>> On 05.04.2018 01:29, Eric W. Biederman wrote:
>>> Nagarathnam Muthusamy <nagarathnam.muthusamy@oracle.com> writes:
>>>
>>>> On 04/04/2018 12:11 PM, Konstantin Khlebnikov wrote:
>>>>> Each process have different pids, one for each pid namespace it belongs.
>>>>> When interaction happens within single pid-ns translation isn't required.
>>>>> More complicated scenarios needs special handling.
>>>>>
>>>>> For example:
>>>>> - reading pid-files or logs written inside container with pid namespace
>>>>> - attaching with ptrace to tasks from different pid namespace
>>>>> - passing pids across pid namespaces in any kind of API
>>>>>
>>>>> Currently there are several interfaces that could be used here:
>>>>>
>>>>> Pid namespaces are identified by inode number of /proc/[pid]/ns/pid.
>>>
>>> Using the inode number in interfaces is not an option. Especially not
>>> withou referencing the device number for the filesystem as well.
>>
>> This is supposed to be single-instance fs,
>> not part of proc but referenced but its magic "symlinks".
>>
>> Device numbers are not mentioned in "man namespaces".
>
> Thanks for the heads-up!
>
> That was a bug in the man-page. ioctl_ns(2) already says the right thing.
> Now I patches namespaces(7), as below.
Acked-by: "Eric W. Biederman" <ebiederm@xmission.com>
For the changes to namespaces.7. I suspect you have already applied
them by now, but if not.
Eric
> Cheers,
>
> Michael
>
> diff --git a/man7/namespaces.7 b/man7/namespaces.7
> index 725ebaff6..3c155de7e 100644
> --- a/man7/namespaces.7
> +++ b/man7/namespaces.7
> @@ -154,11 +154,14 @@ In Linux 3.7 and earlier, these files were visible as hard links.
> Since Linux 3.8,
> .\" commit bf056bfa80596a5d14b26b17276a56a0dcb080e5
> they appear as symbolic links.
> -If two processes are in the same namespace, then the inode numbers of their
> +If two processes are in the same namespace,
> +then the device IDs and inode numbers of their
> .IR /proc/[pid]/ns/xxx
> symbolic links will be the same; an application can check this using the
> +.I stat.st_dev
> +and
> .I stat.st_ino
> -field returned by
> +fields returned by
> .BR stat (2).
> The content of this symbolic link is a string containing
> the namespace type and inode number as in the following example:
prev parent reply other threads:[~2018-05-31 18:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-04 19:11 [PATCH RFC v5] pidns: introduce syscall translate_pid Konstantin Khlebnikov
2018-04-04 20:31 ` Nagarathnam Muthusamy
2018-04-04 22:29 ` Eric W. Biederman
2018-04-05 7:02 ` Konstantin Khlebnikov
2018-04-23 17:37 ` Nagarathnam Muthusamy
2018-04-25 5:36 ` Konstantin Khlebnikov
2018-05-15 17:19 ` Nagarathnam Muthusamy
2018-05-15 17:36 ` Konstantin Khlebnikov
2018-05-15 17:40 ` Nagarathnam Muthusamy
2018-05-15 17:44 ` Nagarathnam Muthusamy
2018-05-31 17:41 ` Nagarathnam Muthusamy
2018-05-31 17:52 ` Eric W. Biederman
2018-05-31 18:05 ` Eric W. Biederman
2018-06-01 6:58 ` Konstantin Khlebnikov
2018-06-01 15:55 ` NAGARATHNAM MUTHUSAMY
2018-06-01 16:14 ` Eric W. Biederman
2018-06-01 16:15 ` Konstantin Khlebnikov
2018-04-27 12:15 ` Michael Kerrisk (man-pages)
2018-05-31 18:02 ` Eric W. Biederman [this message]
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=871sdrem9y.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=akpm@linux-foundation.org \
--cc=jannh@google.com \
--cc=khlebnikov@yandex-team.ru \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mtk.manpages@gmail.com \
--cc=nagarathnam.muthusamy@oracle.com \
--cc=oleg@redhat.com \
--cc=prakash.sangappa@oracle.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;
as well as URLs for NNTP newsgroup(s).