From owner-freebsd-hackers Thu Apr 6 22:36:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id B037137B8BB for ; Thu, 6 Apr 2000 22:36:39 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e3762Z804586; Thu, 6 Apr 2000 23:02:35 -0700 (PDT) Date: Thu, 6 Apr 2000 23:02:35 -0700 From: Alfred Perlstein To: Gustavo V G C Rios Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Is traditional unixes kernel really stable ? Message-ID: <20000406230234.B4381@fw.wintelcom.net> References: <38ED128C.22C3AA28@tdnet.com.br> <20000406192206.N22104@fw.wintelcom.net> <38ED233E.74716D02@tdnet.com.br> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <38ED233E.74716D02@tdnet.com.br>; from kernel@tdnet.com.br on Thu, Apr 06, 2000 at 11:52:30PM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Gustavo V G C Rios [000406 20:23] wrote: > Alfred Perlstein wrote: > > > > * Gustavo V G C Rios [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