From owner-freebsd-current Mon May 6 8: 3:42 2002 Delivered-To: freebsd-current@freebsd.org Received: from yello.shallow.net (yello.shallow.net [203.18.243.120]) by hub.freebsd.org (Postfix) with ESMTP id DFFF437B403 for ; Mon, 6 May 2002 08:03:39 -0700 (PDT) Received: by yello.shallow.net (Postfix, from userid 1001) id 0804A2A6D; Tue, 7 May 2002 01:03:33 +1000 (EST) Date: Tue, 7 May 2002 01:03:32 +1000 From: Joshua Goodall To: current@freebsd.org Cc: Jeff Roberson Subject: Re: LOOKUP_SHARED is default now Message-ID: <20020506150332.GA38157@roughtrade.net> References: <20020409010420.R16729-100000@mail.chesapeake.net> <20020506065327.GA34586.qhwt@myrealbox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020506065327.GA34586.qhwt@myrealbox.com> User-Agent: Mutt/1.3.28i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, May 06, 2002 at 03:53:27PM +0900, qhwt@myrealbox.com wrote: > I've been struggling upgrading kernel since beginning of April, and finally > found I have to add "options LOOKUP_EXCLUSIVE" to my kernel config file. > Without LOOKUP_EXCLUSIVE, > - some of the processes stall in "inode" state, and can't be killed > by any signals > - shutting down(and maybe unmounting) the system results in the panic: > lockmgr: upgrade exclusive lock > > The stalling processes are all touching files under nullfs-mounted > directories, so I think nullfs code is not yet LOOKUP_SHARED-safe. > If anyone is interested, I can post the backtrace and my kernel config > (after upgrading the world and rebuilding the panicking kernel). If you're feeling experimental try the change in PR kern/37270. It makes nullfs partially safe w.r.t. LOOKUP_SHARED, although there are still easily reproducable deadlocks (possible interactions with the syncer and/or vnlru processes but nothing concrete; at least, not from me). Joshua To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message