From owner-freebsd-bugs  Sun Aug 18 14:40:10 2002
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 7538B37B400
	for <freebsd-bugs@hub.freebsd.org>; Sun, 18 Aug 2002 14:40:07 -0700 (PDT)
Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 31C6B43E77
	for <freebsd-bugs@hub.freebsd.org>; Sun, 18 Aug 2002 14:40:07 -0700 (PDT)
	(envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1])
	by freefall.freebsd.org (8.12.4/8.12.4) with ESMTP id g7ILe7JU073696
	for <freebsd-bugs@freefall.freebsd.org>; Sun, 18 Aug 2002 14:40:07 -0700 (PDT)
	(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.12.4/8.12.4/Submit) id g7ILe7k1073694;
	Sun, 18 Aug 2002 14:40:07 -0700 (PDT)
Date: Sun, 18 Aug 2002 14:40:07 -0700 (PDT)
Message-Id: <200208182140.g7ILe7k1073694@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.org
Cc: 
From: "Tha KreAture" <Tha_KreAture@hotmail.com>
Subject: Re: i386/41723: Copying files to filesystem causes "integer divide fault" and panic.
Reply-To: "Tha KreAture" <Tha_KreAture@hotmail.com>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-bugs.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-bugs>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-bugs>
X-Loop: FreeBSD.org

The following reply was made to PR i386/41723; it has been noted by GNATS.

From: "Tha KreAture" <Tha_KreAture@hotmail.com>
To: <freebsd-gnats-submit@FreeBSD.org>, <kreature@c2i.net>
Cc:  
Subject: Re: i386/41723: Copying files to filesystem causes "integer divide fault" and panic.
Date: Sun, 18 Aug 2002 23:40:46 +0200

 Ahh I see.
 
 Well, then something is afoot.  It may be some emulator or compiler option I
 am using then, that allowed 'long' to deal with the numbers 'int' didn't.
 ???
 
 Anyway:  int was 32 bit and the sum of the calculations could well be too
 large.
 I agree that int64_t is a safer and more precise solution because it is not
 subject to platform differences.
 
 I still believe a check chould be added in the system to make sure it won't
 allow values of avg file size and files pr dir to result in overflows when
 multiplied.  There are other similar calculations all through ffs that
 really need to be addressed.
 
 It's also ridiculus that newfs will segfault if you give it a blocksize
 larger than 65536, but that is a different matter.
 (and probably is already, or will be fixed.)
 
     Kyrre
 
 
 

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message