From: ebiederm@xmission.com (Eric W. Biederman)
To: Nagarathnam Muthusamy <nagarathnam.muthusamy@oracle.com>
Cc: Konstantin Khlebnikov <khlebnikov@yandex-team.ru>,
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:05:17 -0500 [thread overview]
Message-ID: <87po1bd7ky.fsf@xmission.com> (raw)
In-Reply-To: <3bdd6b27-0a46-5802-8671-07268cecc1c7@oracle.com> (Nagarathnam Muthusamy's message of "Thu, 31 May 2018 10:41:20 -0700")
Nagarathnam Muthusamy <nagarathnam.muthusamy@oracle.com> writes:
> Ping? Any additional comments on this patch?
Konstantin's v5 no.
I am uncomfortable with unnecessary flexibility. I don't want to
encourage the increased usage of pids to identify namespaces. I saw
no arguments in favor of pids to identify namespaces from Konstantin.
Your v4 updated to reflect Andrew Morton's concerns in the changelog
yes.
Eric
next prev parent reply other threads:[~2018-05-31 18:05 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 [this message]
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
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=87po1bd7ky.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=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