linux-kernel - Re: [git patches] net driver fixes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080916154342.GD1400@cs181140183.pp.htv.fi>
Date:	Tue, 16 Sep 2008 18:43:42 +0300
From:	Adrian Bunk <bunk@...nel.org>
To:	Arjan van de Ven <arjan@...radead.org>
Cc:	Theodore Tso <tytso@....edu>, Jarek Poplawski <jarkao2@...il.com>,
	Thomas Bogendoerfer <tsbogend@...ha.franken.de>,
	David Miller <davem@...emloft.net>, jeff@...zik.org,
	netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [git patches] net driver fixes

On Tue, Sep 16, 2008 at 07:48:02AM -0700, Arjan van de Ven wrote:
> On Tue, 16 Sep 2008 17:34:10 +0300
> Adrian Bunk <bunk@...nel.org> wrote:
>...
> > 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 list is helpful, and improving it is great, but it will 
never be able to cover 100% of all problems on 100% of all computers.

> > 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. 

You miss my point:

We agree that the kerneloops list is not perfect.

And usually the bugs with a trace that go into the list are the
ones that are easier to debug and fix, while the others might be
much harder to debug.

If one takes Linus' "simple rule of thumb" literally then a hard to 
debug bug without any messages anywhere mustn't be fixed outside of
a merge window. This literal reading is what doesn't make sense.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/