From owner-freebsd-hackers@FreeBSD.ORG Fri May 9 07:42:59 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A128337B401 for ; Fri, 9 May 2003 07:42:59 -0700 (PDT) Received: from internetDog.org (CPE00010230ac1b-CM014490005040.cpe.net.cable.rogers.com [24.102.167.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7BBB443F85 for ; Fri, 9 May 2003 07:42:58 -0700 (PDT) (envelope-from alih@internetDog.org) Received: from alih by internetDog.org with local (Exim 3.12 #1 (Debian)) id 19E95d-0000bZ-00 for ; Fri, 09 May 2003 10:43:13 -0400 Date: Fri, 9 May 2003 10:43:13 -0400 From: Ali Bahar To: freebsd-hackers@freebsd.org Message-ID: <20030509104313.B1465@internetDog.org> Mail-Followup-To: freebsd-hackers@freebsd.org References: <20030508150341.B28906@internetDog.org> <1789.1052421172@critter.freebsd.dk> <20030508195410.A670@internetDog.org> <20030509064025.GA91122@walton.maths.tcd.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20030509064025.GA91122@walton.maths.tcd.ie>; from dwmalone@maths.tcd.ie on Fri, May 09, 2003 at 07:40:25AM +0100 Subject: Re: cache_purge > cache_zap segmentation fault X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: alih@internetDog.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 May 2003 14:42:59 -0000 On Fri, May 09, 2003 at 07:40:25AM +0100, David Malone wrote: > On Thu, May 08, 2003 at 07:54:10PM -0400, Ali Bahar wrote: > > Considering its increasing frequency, I even suspected that the > > filesystem had been corrupted -- in a way undetected by fsck. But, a > To me it seems very unlikely that a corrupted filesystem would > result in a corrupted name cache. The name cache is independendent I understand, and agree. > Mind you, I couldn't say for certain that some subtle corruption > might not cause the problem. _My_ perspective, too -- especially since I'm ignorant about the filesystem code. :-) > Is it possible that one of your modules is somehow stomping on > memory that doesn't belong to it? (Phrasing the right question is indeed half the solution.) Excellent. Though this ought have been obvious to me, somehow I never considered it plausible. Perhaps due to the presumed 'distance' between the filesystem code, and my networking module! :-) The possibility of memory overwrite by an in-development module is about 3 orders of magnitude higher than the possibility of a name cache bug. I can't yet see how it is happening, but I've seen weirder coincidences in scribblers. I'll look into this. Thanks much for your help. Much appreciated. regards, ali -- Jesus was an Arab.