[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.61.0612141815100.12730@yvahk01.tjqt.qr>
Date: Thu, 14 Dec 2006 18:17:08 +0100 (MET)
From: Jan Engelhardt <jengelh@...ux01.gwdg.de>
To: Arjan van de Ven <arjan@...radead.org>
cc: Alan <alan@...rguk.ukuu.org.uk>,
Hans-Jürgen Koch <hjk@...utronix.de>,
Hua Zhong <hzhong@...il.com>,
"'Martin J. Bligh'" <mbligh@...igh.org>,
"'Linus Torvalds'" <torvalds@...l.org>,
"'Greg KH'" <gregkh@...e.de>, "'Jonathan Corbet'" <corbet@....net>,
"'Andrew Morton'" <akpm@...l.org>,
"'Michael K. Edwards'" <medwards.linux@...il.com>,
linux-kernel@...r.kernel.org
Subject: Re: GPL only modules [was Re: [GIT PATCH] more Driver core patches
for 2.6.19]
On Dec 14 2006 14:10, Arjan van de Ven wrote:
>On Thu, 2006-12-14 at 13:55 +0100, Jan Engelhardt wrote:
>> >On Thu, 14 Dec 2006 12:31:16 +0100
>> >Hans-Jürgen Koch wrote:
>> >
>> >You think its any easier to debug because the code now runs in ring 3 but
>> >accessing I/O space.
>>
>> A NULL fault won't oops the system,
>
>.. except when the userspace driver crashes as a result and then the hw
>still crashes the hw (for example via an irq storm or by tying the PCI
>bus or .. )
hw crashes the hw? Anyway, yes it might happen, the more with non-NULL pointers
(dangling references f.ex.)
However, if the userspace part is dead, no one acknowledges the irq, hence an
irq storm (if not caused by writing bogus stuff into registers) should not
happen.
>
>
-`J'
--
Powered by blists - more mailing lists