From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arjan van de Ven Subject: Re: [git patches] net driver fixes Date: Tue, 16 Sep 2008 07:48:02 -0700 Message-ID: <20080916074802.200c8a43@infradead.org> References: <20080916104811.GC7397@cs181140183.pp.htv.fi> <20080916114305.GB10965@ff.dom.local> <20080916121528.GD7397@cs181140183.pp.htv.fi> <20080916135408.GB13388@mit.edu> <20080916070241.3e8d5202@infradead.org> <20080916143408.GA1400@cs181140183.pp.htv.fi> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Theodore Tso , Jarek Poplawski , Thomas Bogendoerfer , David Miller , jeff@garzik.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, Linus Torvalds To: Adrian Bunk Return-path: Received: from casper.infradead.org ([85.118.1.10]:37059 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752640AbYIPOs0 (ORCPT ); Tue, 16 Sep 2008 10:48:26 -0400 In-Reply-To: <20080916143408.GA1400@cs181140183.pp.htv.fi> Sender: netdev-owner@vger.kernel.org List-ID: On Tue, 16 Sep 2008 17:34:10 +0300 Adrian Bunk wrote: > On Tue, Sep 16, 2008 at 07:02:41AM -0700, Arjan van de Ven wrote: > > On Tue, 16 Sep 2008 09:54:08 -0400 > > Theodore Tso wrote: > > > > > If it's a really important bug, and it affects a huge number of > > > users, or it's really bad security bug, the reality is that > > > exceptions will be made to the rules. But exceptions need to > > > remain exceptions for extraordinary situations, not everyday > > > occurrences. And of course, if the bug does affect a huge number > > > of users, someone should be asking the question why it wasn't > > > detected sooner, say before the last merge window --- and to ask > > > the question how many users is this bug really going to affect > > > anyway? > > > > > > At least, that's my take on things, > > > > > > > also note that Linus said "regression or on the kerneloops list"; > > if it has any kind of backtrace, it'll be there if it's a common > > problem that hits many users. > > Thomas' patch [1] will fixes a bug of a kind that will likely never > make it to your list. not sure; just we need to catch doing pci_disable_device on a non-enabled device as a WARN_ON. and the patch looks quite wrong, the real answer should be to do the enable in open() :-) > > And the same also e.g. goes for bugs where your machine is completely > dead (no SysRq possible) with nothing in the logs. that's being worked on, by storing the crash data in some non-volatile piece of memory > > The kerneloops lists are quite valuable, but they can never cover all > classes of fatal bugs. if you want perfection, you're not going to get it. "Perfect is the enemy of good" If you want to help make things better (as opposed to perfect), you're very welcome to help out, be it with suggestions on how to improve or with actual code. -- Arjan van de Ven Intel Open Source Technology Centre For development, discussion and tips for power savings, visit http://www.lesswatts.org