From: Marcos Dione Subject: Re: kernel panic in inode_lookup Date: Thu, 30 May 2002 15:19:53 -0300 Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: <20020530181953.GC556@tempest.styx.org.ar> References: <20020530164522.GA6478@tempest.styx.org.ar> <20020530180020.GA13689@ravel.coda.cs.cmu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from pcmam.fsl.org.ar ([192.168.1.8] helo=tempest) by mail.vialibre.org.ar with esmtp (Exim 3.34 #1 (Debian)) id 17DUWi-0005Ac-00 for ; Thu, 30 May 2002 15:19:56 -0300 Received: from mdione by tempest with local (masqmail 0.2.8) id 17DUWf-3HO-00 for ; Thu, 30 May 2002 15:19:53 -0300 To: linux-fsdevel@vger.kernel.org Content-Disposition: inline In-Reply-To: <20020530180020.GA13689@ravel.coda.cs.cmu.edu> List-Id: linux-fsdevel.vger.kernel.org On Thu, May 30, 2002 at 02:00:21PM -0400, Jan Harkes wrote: > On Thu, May 30, 2002 at 01:45:22PM -0300, Marcos Dione wrote: > > return dentry; > > /* ext2 does something like this */ > > return NULL; > > } > > This could be your problem. real_lookup assumes that if you return > anything it is a new dentry that you found in some magical way and drops > the refcount on the old dentry (which happens to be the one you are > returning). If the refcount drops to zero the dentry is up for grabs > at which point you've lost any sanity in the kernel's data structures. zanx for the hint. and don't cc: me, I'm subscribed to the list.