From owner-freebsd-arch@FreeBSD.ORG Tue Mar 29 04:49:13 2005 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8FE9B16A4CE for ; Tue, 29 Mar 2005 04:49:13 +0000 (GMT) Received: from VARK.MIT.EDU (VARK.MIT.EDU [18.95.3.179]) by mx1.FreeBSD.org (Postfix) with ESMTP id 37D0F43D39 for ; Tue, 29 Mar 2005 04:49:13 +0000 (GMT) (envelope-from das@FreeBSD.ORG) Received: from VARK.MIT.EDU (localhost [127.0.0.1]) by VARK.MIT.EDU (8.13.3/8.13.1) with ESMTP id j2T4n6Lv009768; Mon, 28 Mar 2005 23:49:06 -0500 (EST) (envelope-from das@FreeBSD.ORG) Received: (from das@localhost) by VARK.MIT.EDU (8.13.3/8.13.1/Submit) id j2T4n6g8009767; Mon, 28 Mar 2005 23:49:06 -0500 (EST) (envelope-from das@FreeBSD.ORG) Date: Mon, 28 Mar 2005 23:49:05 -0500 From: David Schultz To: Jeff Roberson Message-ID: <20050329044905.GA9730@VARK.MIT.EDU> Mail-Followup-To: Jeff Roberson , Stephan Uphoff , arch@FreeBSD.ORG References: <20050314213038.V20708@mail.chesapeake.net> <1110856553.29804.37784.camel@palm> <1110896909.29804.39143.camel@palm> <1111983665.64310.19.camel@palm> <20050328231118.R54623@mail.chesapeake.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050328231118.R54623@mail.chesapeake.net> cc: arch@FreeBSD.ORG cc: Stephan Uphoff Subject: Re: Freeing vnodes. X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Mar 2005 04:49:13 -0000 On Mon, Mar 28, 2005, Jeff Roberson wrote: > > > I am worried about the v_dd,v_ddid fields of a directory B that has the > > > to be released vnode A as parent. (Obviously in this case there is no > > > namecache entry with the vnode A as the directory (nc_dvp)) > > > > > > Right now A is type stable - but if A is released, access to B->v_dd > > > may cause a page fault. > > > > > > Stephan > > > > Jeff, > > > > Do you plan to address the problem now that the code is checked in? > > Vnodes with children in the name cache are held with vhold() and not > recycled. Yes, but cache_purge() is called directly in a number of places where the vnode may have children, e.g. in mount. So dangling references might still be possible unless cache_purge() fixes up the children's v_dd pointers appropriately.