Date: Mon, 3 Oct 2005 20:28:31 -0700
From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Diego de Estrada <diego1609@gmail.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] release_resource() check for NULL resource
Message-Id: <20051003202831.64d6e5a6.rdunlap@xenotime.net>
In-Reply-To: <5dc44ec70510031959w1f4adfcbh395535ade34a357d@mail.gmail.com>
References: <20051002170318.GA22074@home.fluff.org>
	<20051002103922.34dd287d.rdunlap@xenotime.net>
	<5dc44ec70510031959w1f4adfcbh395535ade34a357d@mail.gmail.com>
Organization: YPO4
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 916
Lines: 27

On Mon, 3 Oct 2005 23:59:16 -0300 Diego de Estrada wrote:

> On 10/2/05, Randy.Dunlap <rdunlap@xenotime.net> wrote:
> > On Sun, 2 Oct 2005 18:03:18 +0100 Ben Dooks wrote:
> >
> > > If release_resource() is passed a NULL resource
> > > the kernel will OOPS.
> >
> > does this actually happen?  you are fixing a real oops?
> > if so, what driver caused it?
> 
> The point is: no driver should make the kernel OOPS. Thanks Ben.

I understand that sentiment, but if a driver is bad,
we generally want to know about that rather than paste
(or paper) over it on a continuous basis.


---
~Randy
You can't do anything without having to do something else first.
-- Belefant's Law
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/