Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030473AbWBNGCF (ORCPT ); Tue, 14 Feb 2006 01:02:05 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1030475AbWBNGCF (ORCPT ); Tue, 14 Feb 2006 01:02:05 -0500 Received: from ebiederm.dsl.xmission.com ([166.70.28.69]:57837 "EHLO ebiederm.dsl.xmission.com") by vger.kernel.org with ESMTP id S1030473AbWBNGCD (ORCPT ); Tue, 14 Feb 2006 01:02:03 -0500 To: "Serge E. Hallyn" Cc: Kirill Korotaev , linux-kernel@vger.kernel.org, vserver@list.linux-vserver.org, Herbert Poetzl , Alan Cox , Dave Hansen , Arjan van de Ven , Suleiman Souhlal , Hubertus Franke , Cedric Le Goater , Kyle Moffett , Greg , Linus Torvalds , Andrew Morton , Greg KH , Rik van Riel , Alexey Kuznetsov , Andrey Savochkin , Kirill Korotaev , Andi Kleen , Benjamin Herrenschmidt , Jeff Garzik , Trond Myklebust , Jes Sorensen Subject: Re: [RFC][PATCH 04/20] pspace: Allow multiple instaces of the process id namespace References: <43ECF803.8080404@sw.ru> <43F04FD6.5090603@sw.ru> <20060213170207.GB24200@sergelap.austin.ibm.com> From: ebiederm@xmission.com (Eric W. Biederman) Date: Mon, 13 Feb 2006 22:59:35 -0700 In-Reply-To: <20060213170207.GB24200@sergelap.austin.ibm.com> (Serge E. Hallyn's message of "Mon, 13 Feb 2006 11:02:07 -0600") Message-ID: User-Agent: Gnus/5.1007 (Gnus v5.10.7) Emacs/21.4 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1097 Lines: 23 > 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/