From: Matthew Wilcox Subject: Re: [2.5.36] oops when reading /proc/locks Date: Thu, 19 Sep 2002 22:54:13 +0100 Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: <20020919225413.H10583@parcelfarce.linux.theplanet.co.uk> References: <20020919211623.B10583@parcelfarce.linux.theplanet.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Matthew Wilcox , Stephen Rothwell , linux-fsdevel@vger.kernel.org Return-path: To: Burton Windle Content-Disposition: inline In-Reply-To: ; from bwindle@fint.org on Thu, Sep 19, 2002 at 05:49:48PM -0400 List-Id: linux-fsdevel.vger.kernel.org On Thu, Sep 19, 2002 at 05:49:48PM -0400, Burton Windle wrote: > OK. Re-compiled the entire kernel with 2.95, and now I get this with > 2.5.36: > > eth0: Setting promiscuous mode. > device eth0 entered promiscuous mode > device eth0 left promiscuous mode > null dentry at 1 > null dentry at 1 what lock shows up at entry 1 on the list, and then what PID is it? Can you get the command name for that pid, eg cat /proc//cmdline? -- Revolutions do not require corporate support.