linux-kernel - Re: BUG in 2.6.29 final: broken network connection

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>] [day] [month] [year] [list]

Message-ID: <20090324214536.GA29509@elte.hu>
Date:	Tue, 24 Mar 2009 22:45:36 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	sinter <sinter.salt@....de>
Cc:	Alan Cox <alan@...rguk.ukuu.org.uk>, linux-kernel@...r.kernel.org,
	"David S. Miller" <davem@...emloft.net>,
	Herbert Xu <herbert@...dor.apana.org.au>,
	netdev@...r.kernel.org
Subject: Re: BUG in 2.6.29 final: broken network connection

* sinter <sinter.salt@....de> wrote:

> > And there's an easy solution for you in any case: you can wait 
> > for .29.1 which i'm sure will be out quickly.
> 
> And what top-class advice would you give me if I would have found 
> that serious bug in .29.8 or in .29.9? Due to your answer every 
> shit is possible and nothing is impossible, or did I get something 
> wrong?

You got it exactly right.

This world is ruled by probabilities, and generally everything is 
possible - even a bug slipping into a .0 release that you could 
trigger personally, even though -rc1 through -rc8 worked just fine 
for you.

Such things happened before, and they can happen again. Yes, it can 
hit you - and it did hit me too and i'm not complaining.

We still try our best to reduce the probabilities. We cannot, 
however, unfortunately, bring them down to zero. The fix looked 
reasonable and the justification of it fixing a live crash looked 
reasonable too.

What we can do, and what we did do, was to provide people (you 
included) with a fix within 12 hours after the code having been 
released.

That's the deal really.

	Ingo
--
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/