From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262500AbULRArW (ORCPT ); Fri, 17 Dec 2004 19:47:22 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262793AbULRArW (ORCPT ); Fri, 17 Dec 2004 19:47:22 -0500 Received: from holomorphy.com ([207.189.100.168]:35802 "EHLO holomorphy.com") by vger.kernel.org with ESMTP id S262500AbULRArK (ORCPT ); Fri, 17 Dec 2004 19:47:10 -0500 Date: Fri, 17 Dec 2004 16:47:03 -0800 From: William Lee Irwin III To: Brent Casavant Cc: linux-kernel@vger.kernel.org, mingo@elte.hu Subject: Re: Oops on 2.4.x invalid procfs i_ino value Message-ID: <20041218004703.GE771@holomorphy.com> References: <20041218003835.GD771@holomorphy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041218003835.GD771@holomorphy.com> Organization: The Domain of Holomorphy User-Agent: Mutt/1.5.6+20040722i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Dec 17, 2004 at 04:49:44PM -0600, Brent Casavant wrote: >> On a related note, if it matters, on about half the crash dumps I've >> looked at, I see a pid of 0 has been assigned to a user process, >> tripping this same problem. I suspect there's another bug somewhere >> that's allowing a pid of 0 to be chosen in the first place -- but I >> don't totally discount that this problem may lay in SGI's patches to >> this particular kernel -- I'll need to take a more thorough look. On Fri, Dec 17, 2004 at 04:38:35PM -0800, William Lee Irwin III wrote: > That's rather ominous. I'll pore over pid.c and see what's going on. > Also, does the pid.c in your kernel version match 2.6.x-CURRENT? Ouch, 2.4.21; this will be trouble. So next, what patches atop 2.4.21? -- wli