OpenVZ Forum - RDF feed
type: channel
items: [PATCH] pid: Extend/Fix pid_vnr
items: Re: [PATCH] pid: Extend/Fix pid_vnr
items: [PATCH] sys_getsid: don't use ->nsproxy directly

[PATCH] pid: Extend/Fix pid_vnr
type: item
description: pid_vnr returns the user space pid with respect to the pid namespace the struct pid was allocated in. What we want before we return a pid to user space is the user space pid with respect to the pid namespace of current. pid_vnr is a very nice optimization but because it isn't quite what we want it is easy to use pid_vnr at times when we aren't certain the struct pid was allocated in our pid namespace. Currently this describes at least tiocgpgrp and tiocgsid in ttyio.c the parent process reported in the core dumps and the parent process in get_signal_to_deliver. So unless the performance impact is huge having an interface that does what we want instead of always what we want should be much more reliable and much less error prone. Signed-off-by: Eric W. Biederman <ebiederm@xmission.com> --- include/linux/pid.h | 14 +++----------- include/linux/sched.h | 5 ++--- kernel/pid.c | 6 ++++++ 3 files changed, 11 insertions(+), 14 deletions(-) diff --git a/include/linux/pid.h b/include/linux/pid.h index 061abb6..b91f473 100644 --- a/include/linux/pid.h +++ b/include/linux/pid.h @@ -127,9 +127,8 @@ extern void FASTCALL(free_pid(struct pid *pid)); * the helpers to get the pid's id seen from different namespaces * * pid_nr() : global id, i.e. the id seen from the init namespace; - * pid_vnr() : virtual id, i.e. the id seen from the namespace this pid - * belongs to. this only makes sence when called in the - * context of the task that belongs to the same namespace; + * pid_vnr() : virtual id, i.e. the id seen from the pid namespace of + * current. * pid_nr_ns() : id seen from the ns specified. * * see also task_xid_nr() etc in include/linux/sched.h @@ -144,14 +143,7 @@ static inline pid_t pid_nr(struct pid *pid) } pid_t pid_nr_ns(struct pid *pid, struct pid_namespace *ns); - -static inline pid_t pid_vnr(struct pid *pid) -{ - pid_t nr = 0; - if (pid) - nr = pid->numbers[pid->level].nr; - return nr; -} +pid_t pid_vnr(struct pid *pid); #define do_each_pid_task(pid, type, task) \ do …
creator: ebiederm
date: 2007-12-06T04:51:43-00:00

Re: [PATCH] pid: Extend/Fix pid_vnr
type: item
description: Eric W. Biederman wrote: > pid_vnr returns the user space pid with respect to the pid namespace > the struct pid was allocated in. What we want before we return a pid > to user space is the user space pid with respect to the pid namespace > of current. > > pid_vnr is a very nice optimization but because it isn't quite what we > want it is easy to use pid_vnr at times when we aren't certain the > struct pid was allocated in our pid namespace. > > Currently this describes at least tiocgpgrp and tiocgsid in ttyio.c > the parent process reported in the core dumps and the parent > process in get_signal_to_deliver. > > So unless the performance impact is huge having an interface that does > what we want instead of always what we want should be much more > reliable and much less error prone. > > Signed-off-by: Eric W. Biederman <ebiederm@xmission.com> Yup. xxx_vnr with the existing meaning turns out to be useless. Thanks, Eric. Acked-by: Pavel Emelyanov <xemul@openvz.org> > --- > include/linux/pid.h | 14 +++----------- > include/linux/sched.h | 5 ++--- > kernel/pid.c | 6 ++++++ > 3 files changed, 11 insertions(+), 14 deletions(-) > > diff --git a/include/linux/pid.h b/include/linux/pid.h > index 061abb6..b91f473 100644 > --- a/include/linux/pid.h > +++ b/include/linux/pid.h > @@ -127,9 +127,8 @@ extern void FASTCALL(free_pid(struct pid *pid)); > * the helpers to get the pid's id seen from different namespaces > * > * pid_nr() : global id, i.e. the id seen from the init namespace; > - * pid_vnr() : virtual id, i.e. the id seen from the namespace this pid > - * belongs to. this only makes sence when called in the > - * context of the task that belongs to the same namespace; > + * pid_vnr() : virtual id, i.e. the id seen from the pid namespace of > + * current. > * pid_nr_ns() : id seen from the ns specified. > * > * see also task_xid_nr() etc in include/linux/sched.h > @@ -144,14 +143,7 @@ static inline pid_t pid_nr(struct pid *pid) > } > > pid_t pid_nr_ns(struct pid *pid, s…
creator: Pavel Emelianov
date: 2007-12-06T10:02:03-00:00

Re: [PATCH] pid: Extend/Fix pid_vnr
type: item
description: On 12/05, Eric W. Biederman wrote: > > +pid_t pid_vnr(struct pid *pid) > +{ > + return pid_nr_ns(pid, current->nsproxy->pid_ns); > +} Excellent!!! This allows us to do many cleanups. I am sending the trivial patch just as example. Oleg. _______________________________________________ Containers mailing list Containers@lists.linux-foundation.org https://lists.linux-foundation.org/mailman/listinfo/containers
creator: Oleg Nesterov
date: 2007-12-06T17:15:13-00:00

[PATCH] sys_getsid: don't use ->nsproxy directly
type: item
description: With the new semantics of find_vpid() we don't need to play with ->nsproxy explicitely, _vxx() do the right things. Also s/tasklist/rcu/. Signed-off-by: Oleg Nesterov <oleg@tv-sign.ru> --- PT/kernel/sys.c~ 2007-12-05 21:43:18.000000000 +0300 +++ PT/kernel/sys.c 2007-12-06 20:09:02.000000000 +0300 @@ -1025,19 +1025,16 @@ asmlinkage long sys_getsid(pid_t pid) else { int retval; struct task_struct *p; - struct pid_namespace *ns; - ns = current->nsproxy->pid_ns; - - read_lock(&tasklist_lock); - p = find_task_by_pid_ns(pid, ns); + rcu_read_lock(); + p = find_task_by_vpid(pid); retval = -ESRCH; if (p) { retval = security_task_getsid(p); if (!retval) - retval = task_session_nr_ns(p, ns); + retval = task_session_vnr(p); } - read_unlock(&tasklist_lock); + rcu_read_unlock(); return retval; } } _______________________________________________ Containers mailing list Containers@lists.linux-foundation.org https://lists.linux-foundation.org/mailman/listinfo/containers
creator: Oleg Nesterov
date: 2007-12-06T17:53:14-00:00

Re: [PATCH] pid: Extend/Fix pid_vnr
type: item
description: Oleg Nesterov [oleg@tv-sign.ru] wrote: | On 12/05, Eric W. Biederman wrote: | > | > +pid_t pid_vnr(struct pid *pid) | > +{ | > + return pid_nr_ns(pid, current->nsproxy->pid_ns); | > +} Hmm. current->nsproxy be NULL during process exit ? So this safe as long as pid_vnr() is not called after a process exits its namespaces. Probably no such callers atm. | | Excellent!!! | | This allows us to do many cleanups. I am sending the trivial patch just | as example. | | Oleg. _______________________________________________ Containers mailing list Containers@lists.linux-foundation.org https://lists.linux-foundation.org/mailman/listinfo/containers
creator: Sukadev Bhattiprolu
date: 2007-12-07T01:04:24-00:00

Re: [PATCH] pid: Extend/Fix pid_vnr
type: item
description: Quoting sukadev@us.ibm.com (sukadev@us.ibm.com): > Oleg Nesterov [oleg@tv-sign.ru] wrote: > | On 12/05, Eric W. Biederman wrote: > | > > | > +pid_t pid_vnr(struct pid *pid) > | > +{ > | > + return pid_nr_ns(pid, current->nsproxy->pid_ns); > | > +} > > Hmm. current->nsproxy be NULL during process exit ? > So this safe as long as pid_vnr() is not called after a > process exits its namespaces. Probably no such callers atm. Yes I did a little audit for those this morning bc I frankly didn't believe there weren't any. But I couldn't find any :) -serge > | > | Excellent!!! > | > | This allows us to do many cleanups. I am sending the trivial patch just > | as example. > | > | Oleg. > _______________________________________________ > Containers mailing list > Containers@lists.linux-foundation.org > https://lists.linux-foundation.org/mailman/listinfo/containers _______________________________________________ Containers mailing list Containers@lists.linux-foundation.org https://lists.linux-foundation.org/mailman/listinfo/containers
creator: serue
date: 2007-12-07T01:57:27-00:00

Re: [PATCH] pid: Extend/Fix pid_vnr
type: item
description: "Serge E. Hallyn" <serue@us.ibm.com> writes: > Quoting sukadev@us.ibm.com (sukadev@us.ibm.com): >> Oleg Nesterov [oleg@tv-sign.ru] wrote: >> | On 12/05, Eric W. Biederman wrote: >> | > >> | > +pid_t pid_vnr(struct pid *pid) >> | > +{ >> | > + return pid_nr_ns(pid, current->nsproxy->pid_ns); >> | > +} >> >> Hmm. current->nsproxy be NULL during process exit ? >> So this safe as long as pid_vnr() is not called after a >> process exits its namespaces. Probably no such callers atm. > > Yes I did a little audit for those this morning bc I frankly didn't > believe there weren't any. But I couldn't find any :) Cool. The only case pid_vnr would make sense in that context is if we were talking to user space after we had exited our namespaces. Which is at least as stretch. Eric _______________________________________________ Containers mailing list Containers@lists.linux-foundation.org https://lists.linux-foundation.org/mailman/listinfo/containers
creator: ebiederm
date: 2007-12-07T18:10:09-00:00