Re: [RFC][PATCH 01/20] pid: Intoduce the concept of a wid (wait id)

Quoting Eric W. Biederman ([email protected]):
> 
> 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.

-serge
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [RFC][PATCH 01/20] pid: Intoduce the concept of a wid (wait id)
    • From: [email protected] (Eric W. Biederman)

• References:
  • [RFC][PATCH 0/20] Multiple instances of the process id namespace
    • From: [email protected] (Eric W. Biederman)
  • [RFC][PATCH 01/20] pid: Intoduce the concept of a wid (wait id)
    • From: [email protected] (Eric W. Biederman)

• Prev by Date: Re: Linux drivers management
• Next by Date: [RFC][PATCH 11/20] ioprio: Update ioprio to handle pspaces.
• Previous by thread: Re: [RFC][PATCH 03/20] pid: Introduce a generic helper to test for init.
• Next by thread: Re: [RFC][PATCH 01/20] pid: Intoduce the concept of a wid (wait id)
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]