Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755793AbZCXVrY (ORCPT ); Tue, 24 Mar 2009 17:47:24 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755300AbZCXVpw (ORCPT ); Tue, 24 Mar 2009 17:45:52 -0400 Received: from mx2.mail.elte.hu ([157.181.151.9]:44707 "EHLO mx2.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753160AbZCXVpv (ORCPT ); Tue, 24 Mar 2009 17:45:51 -0400 Date: Tue, 24 Mar 2009 22:45:36 +0100 From: Ingo Molnar To: sinter Cc: Alan Cox , linux-kernel@vger.kernel.org, "David S. Miller" , Herbert Xu , netdev@vger.kernel.org Subject: Re: BUG in 2.6.29 final: broken network connection Message-ID: <20090324214536.GA29509@elte.hu> References: <200903241812.14577.sinter.salt@gmx.de> <200903241918.29929.sinter.salt@gmx.de> <20090324194254.GB26930@elte.hu> <200903242149.59640.sinter.salt@gmx.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200903242149.59640.sinter.salt@gmx.de> User-Agent: Mutt/1.5.18 (2008-05-17) X-ELTE-VirusStatus: clean X-ELTE-SpamScore: -1.5 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-1.5 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.2.3 -1.5 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1368 Lines: 38 * sinter 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/