Messages in this thread | | | Date | Mon, 13 Feb 2006 11:53:29 +0300 | From | Kirill Korotaev <> | Subject | Re: [RFC][PATCH 04/20] pspace: Allow multiple instaces of the process id namespace |
| |
>>>+static inline int pspace_task_visible(struct pspace *pspace, struct >> >>task_struct *tsk) >> >>>+{ >>>+ return (tsk->pspace == pspace) || >>>+ ((tsk->pspace->child_reaper.pspace == pspace) && >>>+ (tsk->pspace->child_reaper.task == tsk)); >> >><<< the logic with child_reaper which can be somehow partly inside pspace... and >>this check is not that abvious. > > > This is the check for what shows up in /proc. > > Given that is how I have explicitly documented things to work, (the > init process straddles the boundary) I fail to see how it is not obvious. I was confused by the fact that child_reaper.pspace is actually a parent pspace.
Kirill
- 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/
| |