From owner-freebsd-hackers  Wed Jul 31 10:31:28 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id KAA11638
          for hackers-outgoing; Wed, 31 Jul 1996 10:31:28 -0700 (PDT)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA11632;
          Wed, 31 Jul 1996 10:31:23 -0700 (PDT)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA02343; Wed, 31 Jul 1996 10:29:46 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199607311729.KAA02343@phaeton.artisoft.com>
Subject: Re: anyone working on upgrading the msdosfs to NetBSD levels?
To: bde@zeta.org.au (Bruce Evans)
Date: Wed, 31 Jul 1996 10:29:45 -0700 (MST)
Cc: rnordier@iafrica.com, terry@lambert.org, current@FreeBSD.org,
        hackers@FreeBSD.org
In-Reply-To: <199607310837.SAA12179@godzilla.zeta.org.au> from "Bruce Evans" at Jul 31, 96 06:37:27 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
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.

The sd and od strategy rotutines do not error out.

I am not sure I trust dscheck() entirely (since corruption occurs).


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.