From owner-freebsd-bugs@FreeBSD.ORG Thu Jul 31 06:30:18 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 6828837B401 for ; Thu, 31 Jul 2003 06:30:18 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0B6DF43F85 for ; Thu, 31 Jul 2003 06:30:18 -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 h6VDUHUp072153 for ; Thu, 31 Jul 2003 06:30:17 -0700 (PDT) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h6VDUHEJ072146; Thu, 31 Jul 2003 06:30:17 -0700 (PDT) Date: Thu, 31 Jul 2003 06:30:17 -0700 (PDT) Message-Id: <200307311330.h6VDUHEJ072146@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Dmitry Morozovsky Subject: Re: bin/55078: [patch] mount_mfs crashes RELENG_4 for tyny mfs X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Dmitry Morozovsky List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jul 2003 13:30:18 -0000 The following reply was made to PR bin/55078; it has been noted by GNATS. From: Dmitry Morozovsky To: Yar Tikhiy Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: bin/55078: [patch] mount_mfs crashes RELENG_4 for tyny mfs Date: Thu, 31 Jul 2003 17:27:46 +0400 (MSD) On Thu, 31 Jul 2003, Yar Tikhiy wrote: YT> As long as you have investigated the problem: Don't you think that YT> the kernel code must be fixed to keep from crashing as well? Of YT> course, the kernel FS code can't handle all sorts of inconsistency, YT> but if a particular check is easy enough, it should be implemented, YT> to my mind. Surely I think the kernel should be fixed as well; however, in this particular case, it seems to be intentional panic: /mnt: bad dir ino 2 at offset 0: mangled entry panic: ufs_dirbad: bad dir from ufs_lookup.c:641 Also, I'm not ufs hacker, so I'm afraid can't fix this part of kernel myself; however, I'll be glad to help fixing. Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------