From owner-freebsd-bugs  Wed Feb  5 16:02:06 1997
Return-Path: <owner-bugs>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id QAA25460
          for bugs-outgoing; Wed, 5 Feb 1997 16:02:06 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA25446
          for <freebsd-bugs@freefall.freebsd.org>; Wed, 5 Feb 1997 16:02:00 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id KAA26426; Thu, 6 Feb 1997 10:52:29 +1100
Date: Thu, 6 Feb 1997 10:52:29 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199702052352.KAA26426@godzilla.zeta.org.au>
To: freebsd-bugs@freefall.freebsd.org, Shimon@i-Connect.Net
Subject: Re: bin/2633: fsck -p in /etc/rc fails with cannot alloc nnnn by
Sender: owner-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> Have you considered looking at the fact that fsck may be doing lseek or
> some other computation, based on the SIZE of the partition in bytes,
> encountering an integer overflow, or sign extention problem and trying to
> malloc (for example) a negative number, or a very small one, etc.
> 
> Do we have llseek(2) in FreeBSD?

BSD4.4Lite-derived systems have 64-bit off_t's and lseek(2).

There are several overflow and sign extension bugs in plain BSD4.4Lite,
but FreeBSD has fixed many of them.  The most common bug was to do an
overflowing multiplication of a daddr_t by a block size.  fsck and many
other things didn't work for partitions >= 2GB in early versions of
FreeBSD because btodb() in <machine/param.h> overflowed on 32-bit
systems.  There are probably still bugs for files >= 2GB but I don't
know of any for file systems >= 2GB.

Bruce