Messages in this thread | | | Subject | Re: [RFC][PATCH 01/20] pid: Intoduce the concept of a wid (wait id) | From | (Eric W. Biederman) | Date | Mon, 06 Feb 2006 13:23:48 -0700 |
| |
"Serge E. Hallyn" <serue@us.ibm.com> writes:
> Quoting Eric W. Biederman (ebiederm@xmission.com): >> >> The wait id is the pid returned by wait. For tasks that span 2 >> namespaces (i.e. the process leaders of the pid namespaces) their >> parent knows the task by a different PID value than the task knows >> itself. Having a child with PID == 1 would be confusing. > > Is it possible here to have wid conflicts? > > Does that matter? > > Looking at sysvinit, it seems that it does. If the wid happens > to conflict with the pid of one of the children init knows about, > it could confuse init.
No. The wid is in the pspace of the parent, and the pid is in the processes pspace. Add is in any pspace are unique.
Eric - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |