From owner-freebsd-hackers@FreeBSD.ORG  Thu May  8 23:40:27 2003
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
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 2F4C337B401
	for <freebsd-hackers@freebsd.org>;
	Thu,  8 May 2003 23:40:27 -0700 (PDT)
Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11])
	by mx1.FreeBSD.org (Postfix) with SMTP id 1432843FAF
	for <freebsd-hackers@freebsd.org>;
	Thu,  8 May 2003 23:40:26 -0700 (PDT)
	(envelope-from dwmalone@maths.tcd.ie)
Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP
          id <aa84118@salmon>; 9 May 2003 07:40:25 +0100 (BST)
Date: Fri, 9 May 2003 07:40:25 +0100
From: David Malone <dwmalone@maths.tcd.ie>
To: freebsd-hackers@freebsd.org
Message-ID: <20030509064025.GA91122@walton.maths.tcd.ie>
References: <20030508150341.B28906@internetDog.org>
	<1789.1052421172@critter.freebsd.dk> <20030508195410.A670@internetDog.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030508195410.A670@internetDog.org>
User-Agent: Mutt/1.5.3i
Sender: dwmalone@maths.tcd.ie
Subject: Re: cache_purge > cache_zap segmentation fault
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 09 May 2003 06:40:27 -0000

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
> 'normal' filesystem corruption exhibits _random_ crashes, not ones
> consistently following the above execution thread.

To me it seems very unlikely that a corrupted filesystem would
result in a corrupted name cache. The name cache is independendent
of the filesystem and is only populated as lookups in the filesystem
code complete. If there were a problem it seems more likely that
either fsck, the filesystem code or dirhash would catch the problem.
Mind you, I couldn't say for certain that some subtle corruption
might not cause the problem.

Is it possible that one of your modules is somehow stomping on
memory that doesn't belong to it?

	David.