From owner-freebsd-bugs@FreeBSD.ORG Sun May 11 01:20:12 2003 Return-Path: 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 CCABB37B401 for ; Sun, 11 May 2003 01:20:12 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7286A43FBD for ; Sun, 11 May 2003 01:20:12 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h4B8KBUp024959 for ; Sun, 11 May 2003 01:20:11 -0700 (PDT) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h4B8KBgB024958; Sun, 11 May 2003 01:20:11 -0700 (PDT) Date: Sun, 11 May 2003 01:20:11 -0700 (PDT) Message-Id: <200305110820.h4B8KBgB024958@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Valentin Nechayev 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 Reply-To: Valentin Nechayev List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 May 2003 08:20:13 -0000 The following reply was made to PR kern/51016; it has been noted by GNATS. From: Valentin Nechayev To: Ted Mittelstaedt Cc: freebsd-gnats-submit@freebsd.org Subject: Re: kern/51016: kernel panic: ufsdirhash_lookup: bad offset in hash array Date: Sun, 11 May 2003 11:13:49 +0300 Sat, May 10, 2003 at 11:50:12, tedm (Ted Mittelstaedt) wrote about "RE: kern/51016: kernel panic: ufsdirhash_lookup: bad offset in hash array": >>If some port can cause a system crash it's probably a kernel >>security bug and >>it's have to be fixed imho. In any case it can't be classified as port bug, as you suggested in previous letter, unless program has direct access to kernel memory or raw disks. I don't believe he run leafnode as root. TM> This is true if the port crashes on every FreeBSD system it TM> is tried on. Totally wrong. Problem can be triggered with specific config or specific running history. It even can be irreproduceable, if it can be diagnosed. If it is reproduceable, it can be diagnosed much easier. TM> However if your system is the only one that is TM> crashing then it's most likely something specific to your TM> system. This is also possible but you haven't *any* real arguments "pro" it. -netch-