From: Matthew Wilcox Subject: Re: [2.5.36] oops when reading /proc/locks Date: Fri, 20 Sep 2002 17:39:28 +0100 Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: <20020920173928.L10583@parcelfarce.linux.theplanet.co.uk> References: <20020919231949.I10583@parcelfarce.linux.theplanet.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Matthew Wilcox , linux-fsdevel@vger.kernel.org Return-path: To: Burton Windle Content-Disposition: inline In-Reply-To: ; from bwindle@fint.org on Fri, Sep 20, 2002 at 09:38:15AM -0400 List-Id: linux-fsdevel.vger.kernel.org On Fri, Sep 20, 2002 at 09:38:15AM -0400, Burton Windle wrote: > The task that I can reproduce this with is 'ntop'. The system is an > up-to-date Debian Testing. Here is line 1 of /proc/locks while ntop is > running (hand-copied): Hmm.. I'm running Debian too -- unstable rather than testing, but they aren't _that_ far out of sync yet. I installed the ntop from testing and while it's running, I get: 1: POSIX ADVISORY WRITE 506 03:02:261447 0 EOF 2: POSIX ADVISORY WRITE 506 03:02:261449 0 EOF 3: POSIX ADVISORY WRITE 506 03:02:261451 0 EOF 4: POSIX ADVISORY WRITE 506 03:02:261448 0 EOF 5: POSIX ADVISORY WRITE 506 03:02:259887 0 EOF 6: POSIX ADVISORY WRITE 506 03:02:259560 0 EOF (from the ntop process, obviously i have other locks) After I kill ntop, all these locks are gone, which is what i expect ;-( > 1: POSIX ADVISTORY WRITE 271 03:02:17197 0 EOF > > and here is line 1 after ntop is stopped, and after the 'null dentry' > error shows up: > > 1: POSIX *NOINODE* WRITE 271 :0 0 EOF This is good to see... we're not chasing ghosts at least. > Do you want the entire strace, or just when the program is exiting? I think I need the entire strace. please send it gzipped and attached (off-list). thanks! -- Revolutions do not require corporate support.