All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konstantin Khlebnikov <khlebnikov@yandex-team.ru>
To: Oleg Nesterov <oleg@redhat.com>
Cc: linux-api@vger.kernel.org, linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Serge Hallyn <serge.hallyn@ubuntu.com>,
	Nagarathnam Muthusamy <nagarathnam.muthusamy@oracle.com>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	Eugene Syromiatnikov <esyr@redhat.com>
Subject: Re: [PATCH v4] pidns: introduce syscall translate_pid
Date: Fri, 13 Oct 2017 19:13:07 +0300	[thread overview]
Message-ID: <3bdb5341-9ae6-265a-ce5b-45c2cfc76fad@yandex-team.ru> (raw)
In-Reply-To: <20171013160514.GA27812@redhat.com>



On 13.10.2017 19:05, Oleg Nesterov wrote:
> On 10/13, Konstantin Khlebnikov wrote:
>>
>> pid_t translate_pid(pid_t pid, int source, int target);
>>
>> This syscall converts pid from source pid-ns into pid in target pid-ns.
>> If pid is unreachable from target pid-ns it returns zero.
>>
>> Pid-namespaces are referred file descriptors opened to proc files
>> /proc/[pid]/ns/pid or /proc/[pid]/ns/pid_for_children. Negative argument
>> refers to current pid namespace, same as file /proc/self/ns/pid.
>>
>> Kernel expose virtual pids in /proc/[pid]/status:NSpid, but backward
>> translation requires scanning all tasks. Also pids could be translated
>> by sending them through unix socket between namespaces, this method is
>> slow and insecure because other side is exposed inside pid namespace.
>>
>> Examples:
>> translate_pid(pid, ns, -1)      - get pid in our pid namespace
>> translate_pid(pid, -1, ns)      - get pid in other pid namespace
>> translate_pid(1, ns, -1)        - get pid of init task for namespace
>> translate_pid(pid, -1, ns) > 0  - is pid is reachable from ns?
>> translate_pid(1, ns1, ns2) > 0  - is ns1 inside ns2?
>> translate_pid(1, ns1, ns2) == 0 - is ns1 outside ns2?
>> translate_pid(1, ns1, ns2) == 1 - is ns1 equal ns2?
> 
> Add Eugene, strace probably wants this too.
> 
> I have a vague feeling we have already discussed this in the past, but
> I can't recall anything...

Yeah, v3 was two years ago.

> 
>> +static struct pid_namespace *get_pid_ns_by_fd(int fd)
>> +{
>> +	struct pid_namespace *pidns;
>> +	struct ns_common *ns;
>> +	struct file *file;
>> +
>> +	file = proc_ns_fget(fd);
>> +	if (IS_ERR(file))
>> +		return ERR_CAST(file);
>> +
>> +	ns = get_proc_ns(file_inode(file));
>> +	if (ns->ops->type == CLONE_NEWPID)
>> +		pidns = get_pid_ns(to_pid_ns(ns));
>> +	else
>> +		pidns = ERR_PTR(-EINVAL);
>> +
>> +	fput(file);
>> +	return pidns;
>> +}
> 
> I won't insist, but this suggests we should add a new helper,
> get_ns_by_fd_type(fd, type), and convert get_net_ns_by_fd() to use it
> as well.

That was in v3.

I'll prefer to this later, separately. And replace fget with fdget which
allows to do this without atomic operations if task is single-threaded.

> 
>> +SYSCALL_DEFINE3(translate_pid, pid_t, pid, int, source, int, target)
>> +{
>> +	struct pid_namespace *source_ns, *target_ns;
>> +	struct pid *struct_pid;
>> +	pid_t result;
>> +
>> +	if (source >= 0) {
>> +		source_ns = get_pid_ns_by_fd(source);
>> +		result = PTR_ERR(source_ns);
>> +		if (IS_ERR(source_ns))
>> +			goto err_source;
>> +	} else
>> +		source_ns = task_active_pid_ns(current);
>> +
>> +	if (target >= 0) {
>> +		target_ns = get_pid_ns_by_fd(target);
>> +		result = PTR_ERR(target_ns);
>> +		if (IS_ERR(target_ns))
>> +			goto err_target;
>> +	} else
>> +		target_ns = task_active_pid_ns(current);
>> +
>> +	rcu_read_lock();
>> +	struct_pid = find_pid_ns(pid, source_ns);
>> +	result = struct_pid ? pid_nr_ns(struct_pid, target_ns) : -ESRCH;
>> +	rcu_read_unlock();
> 
> Stupid question. Can't we make a simpler API which doesn't need /proc/ ?
> I mean,
> 
> 	sys_translate_pid(pid_t pid, pid_t source_pid, pid_t target_pid)
> 	{
> 		struct pid_namespace *source_ns, *target_ns;
> 
> 		source_ns = task_active_pid_ns(find_task_by_vpid(source_pid));
> 		target_ns = task_active_pid_ns(find_task_by_vpid(target_pid));
> 
> 		...
> 	}
>  > Yes, this is more limited... Do you have a use-case when this is not enough?

That was in v1 but considered too racy.

 >> v1: https://lkml.org/lkml/2015/9/15/411
 >> v2: https://lkml.org/lkml/2015/9/24/278
 >> v3: https://lkml.org/lkml/2015/9/28/3

  reply	other threads:[~2017-10-13 16:13 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-13  9:26 [PATCH v4] pidns: introduce syscall translate_pid Konstantin Khlebnikov
2017-10-13  9:28 ` Konstantin Khlebnikov
2017-10-13 16:05 ` Oleg Nesterov
2017-10-13 16:13   ` Konstantin Khlebnikov [this message]
2017-10-14  8:17     ` Konstantin Khlebnikov
2017-10-14  8:17       ` Konstantin Khlebnikov
2017-10-16 21:36       ` Andrew Morton
2017-10-16 21:36         ` Andrew Morton
2017-10-16 22:07         ` Nagarathnam Muthusamy
2017-10-16 22:07           ` Nagarathnam Muthusamy
2017-10-16 22:54           ` prakash.sangappa
2017-10-17  0:52             ` Andy Lutomirski
2017-10-17  0:52               ` Andy Lutomirski
2017-10-17 15:38               ` Prakash Sangappa
2017-10-17 22:02                 ` Andy Lutomirski
2017-10-17 22:02                   ` Andy Lutomirski
2017-10-17 22:35                   ` prakash sangappa
2017-10-17 22:35                     ` prakash sangappa
2017-10-17 22:40                     ` Andy Lutomirski
2017-10-17 22:40                       ` Andy Lutomirski
2017-10-17 22:53                       ` prakash sangappa
2017-10-17 22:53                         ` prakash sangappa
2017-11-01 16:59                         ` nagarathnam muthusamy
2017-11-01 17:43                 ` Jann Horn
2017-11-02  0:38                   ` prakash.sangappa
2017-10-16 16:24     ` Oleg Nesterov
2017-10-16 16:24       ` Oleg Nesterov
2017-10-16 21:05       ` Nagarathnam Muthusamy
2017-10-16 21:05         ` Nagarathnam Muthusamy
2017-10-17  7:41         ` Konstantin Khlebnikov

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=3bdb5341-9ae6-265a-ce5b-45c2cfc76fad@yandex-team.ru \
    --to=khlebnikov@yandex-team.ru \
    --cc=akpm@linux-foundation.org \
    --cc=ebiederm@xmission.com \
    --cc=esyr@redhat.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nagarathnam.muthusamy@oracle.com \
    --cc=oleg@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.