Date: Thu, 6 Apr 2000 23:02:35 -0700 From: Alfred Perlstein <bright@wintelcom.net> To: Gustavo V G C Rios <kernel@tdnet.com.br> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Is traditional unixes kernel really stable ? Message-ID: <20000406230234.B4381@fw.wintelcom.net> In-Reply-To: <38ED233E.74716D02@tdnet.com.br>; from kernel@tdnet.com.br on Thu, Apr 06, 2000 at 11:52:30PM %2B0000 References: <38ED128C.22C3AA28@tdnet.com.br> <20000406192206.N22104@fw.wintelcom.net> <38ED233E.74716D02@tdnet.com.br>
next in thread | previous in thread | raw e-mail | index | archive | help
* Gustavo V G C Rios <kernel@tdnet.com.br> [000406 20:23] wrote: > Alfred Perlstein wrote: > > > > * Gustavo V G C Rios <kernel@tdnet.com.br> [000406 19:12] wrote: > > > Considering the current kernel design approach used by traditional > > > system, what happens if a drive were wrongly coded ? > > > > > > Would the entiry system crash ? > > > > please define "wrongly coded". > > Definition: the driver tries to access a memory outside its memory > space. Some archs (such as i386) allow the OS to set page protections and io permission bitmaps that effectively can pretect against problems with drivers touching incorrect IO ranges, however... > > Worse yet: What about hardware buggy devices? > This could case the entiry system to crash, isn't it ? Yes, incorrectly programmed hardware either by firmware (on chip/board) or by drivers can cause crashes and hardware damage. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000406230234.B4381>