Date: Wed, 31 Jul 1996 10:29:45 -0700 (MST) From: Terry Lambert <terry@lambert.org> To: bde@zeta.org.au (Bruce Evans) Cc: rnordier@iafrica.com, terry@lambert.org, current@FreeBSD.org, hackers@FreeBSD.org Subject: Re: anyone working on upgrading the msdosfs to NetBSD levels? Message-ID: <199607311729.KAA02343@phaeton.artisoft.com> In-Reply-To: <199607310837.SAA12179@godzilla.zeta.org.au> from "Bruce Evans" at Jul 31, 96 06:37:27 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> >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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199607311729.KAA02343>