From owner-freebsd-bugs@FreeBSD.ORG  Tue Oct 21 02:40:56 2003
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 14A3616A4B3; Tue, 21 Oct 2003 02:40:56 -0700 (PDT)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 8618243FBD; Tue, 21 Oct 2003 02:40:55 -0700 (PDT)
	(envelope-from dwmalone@FreeBSD.org)
Received: from freefall.freebsd.org (dwmalone@localhost [127.0.0.1])
	by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h9L9etFY013955;
	Tue, 21 Oct 2003 02:40:55 -0700 (PDT)
	(envelope-from dwmalone@freefall.freebsd.org)
Received: (from dwmalone@localhost)
	by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h9L9es7w013951;
	Tue, 21 Oct 2003 02:40:54 -0700 (PDT)
	(envelope-from dwmalone)
Date: Tue, 21 Oct 2003 02:40:54 -0700 (PDT)
From: David Malone <dwmalone@FreeBSD.org>
Message-Id: <200310210940.h9L9es7w013951@freefall.freebsd.org>
To: alexovch@ic.kharkov.ua, dwmalone@FreeBSD.org,
	freebsd-bugs@FreeBSD.org
Subject: Re: kern/51016: kernel panic: ufsdirhash_lookup: bad offset in hash
	array
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Oct 2003 09:40:56 -0000

Synopsis: kernel panic: ufsdirhash_lookup: bad offset in hash array

State-Changed-From-To: open->closed
State-Changed-By: dwmalone
State-Changed-When: Tue Oct 21 02:37:52 PDT 2003
State-Changed-Why: 
Based on the core file that I examined for Aleksey and some testing,
we're now pretty cetrain that this problem was caused by ipfw2
writing to memory it had already freed. Upgrading to revieion
1.6.2.18 of ip_fw2.c seems to have fixed the problem.

http://www.freebsd.org/cgi/query-pr.cgi?pr=51016