mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: sinter <sinter.salt@gmx.de>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-kernel@vger.kernel.org,
	"David S. Miller" <davem@davemloft.net>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	netdev@vger.kernel.org
Subject: Re: BUG in 2.6.29 final: broken network connection
Date: Tue, 24 Mar 2009 22:45:36 +0100	[thread overview]
Message-ID: <20090324214536.GA29509@elte.hu> (raw)
In-Reply-To: <200903242149.59640.sinter.salt@gmx.de>


* sinter <sinter.salt@gmx.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

  parent reply	other threads:[~2009-03-24 21:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-24 17:12 sinter
2009-03-24 17:25 ` Alan Cox
2009-03-24 17:40   ` Eric Dumazet
2009-03-24 18:18   ` sinter
2009-03-24 19:42     ` David Miller
2009-03-24 19:42     ` Ingo Molnar
     [not found]       ` <200903242149.59640.sinter.salt@gmx.de>
2009-03-24 21:45         ` Ingo Molnar [this message]
     [not found] <cjisi-2Kz-11@gated-at.bofh.it>
     [not found] ` <cjiC5-2XR-15@gated-at.bofh.it>
     [not found]   ` <cjiVm-3mJ-23@gated-at.bofh.it>
2009-03-24 18:40     ` Niel Lambrechts
2009-03-25 12:30       ` markus reichelt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090324214536.GA29509@elte.hu \
    --to=mingo@elte.hu \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sinter.salt@gmx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®