From owner-freebsd-hackers  Wed Jul 31 02:24:09 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id CAA17644
          for hackers-outgoing; Wed, 31 Jul 1996 02:24:09 -0700 (PDT)
Received: from who.cdrom.com (who.cdrom.com [204.216.27.3])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA17573;
          Wed, 31 Jul 1996 02:23:56 -0700 (PDT)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by who.cdrom.com (8.7.5/8.6.11) with SMTP id BAA01243
          ; Wed, 31 Jul 1996 01:44:40 -0700 (PDT)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id SAA12179; Wed, 31 Jul 1996 18:37:27 +1000
Date: Wed, 31 Jul 1996 18:37:27 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199607310837.SAA12179@godzilla.zeta.org.au>
To: rnordier@iafrica.com, terry@lambert.org
Subject: Re: anyone working on upgrading the msdosfs to NetBSD levels?
Cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>All new FS's should expect to work on a "device" that is totally
>committed to the FS and looks like it starts at offset 0, and return
>EINVAL or EFAULT for out of range operations on the device.  If
>this were there now, then the MSDOSFS would be incapable of
>corrupting non-MSDOSFS disk areas with the current code.

It's always been there.  Broken code can only write outside the range
by corrupting the device number.

Bruce