Messages in this thread | | | Subject | Re: [RFC][PATCH 04/20] pspace: Allow multiple instaces of the process id namespace | From | (Eric W. Biederman) | Date | Mon, 13 Feb 2006 22:59:35 -0700 |
| |
> This seems a very valid point. And even if you implement code to detect > when a process exits whether it is a child_reaper for some pspace, you > can't just make pspace->child_reaper = pspace->child_reaper->child_reaper, > as the wid may not be valid in the grandparent's namespace, right?
Right. What I have done is in the PSPACE_EXIT condition all children when they die self reap and have the global process reaper set to their parent. However since exit_signal == -1 the initial process reaper never sees them.
Even for a nested pspace I figure it is an error for anything to outlive init. The wid not working is a valid reason for this however if it was really necessary a new wid value could be allocated. As nothing on the inside of a pspace is directly aware of it.
The situation is very similar to being behind a NAT firewall.
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/
| |