Re: Linux 2.6.21

Markus Rechberger
2007-04-28T12:51:23Z

On 4/27/07, Adrian Bunk <bunk@stusta.de> wrote:
> On Fri, Apr 27, 2007 at 12:31:43PM -0400, Theodore Tso wrote:
> > On Fri, Apr 27, 2007 at 04:58:05PM +0200, Adrian Bunk wrote:
> > > "no regressions" is definitely not feasible.
> > >
> > > 14 known regressions, some of them not yet debugged at all, are
> > > different from your "some small regression".
> >
> > Yes, but when were some of these regressions reported? Past a certain
> > point, I think it's reasonable to look at the regression, decide how
> > many people would be affected by it, and why it hadn't been noticed
> > earlier, and in some cases, decide that it's better to get this
> > debugged and fixed in the stable and development trees in parallel.
>
> 8 of them have been reported in March or earlier. [1]
>
> Patches for 2 of these 8 were available at the time of the release. [2]
> While the question whether to merge one of them into 2.6.21 was
> controversial, the other one was not controversial.
>

I can imagine that the dvb oops bugfix got held back to avoid some
noise with dvb developers who claimed that they didn't get notified
about how that patch got into the v4l-dvb repository (it didn't get
reviewed by these people for weeks because it simply got ignored and
some of them were aware of that)

On the other side if I read bugreports like the following one:
http://www.mail-archive.com/linux-dvb%40linuxtv.org/msg23028.html

(My Nova-T 500 crashes quite regularly. My machine has been running for
about a week and in that time has had 5 oopses.)

It doesn't solve the Nova-T disconnects, but it at least solves that
the machine doesn't go down when this happens till the driver gets
fixed.
I think it would have been nice to get that patch into it

Markus

> For one of the bugs, it became obvious when someone looked at it after
> the release of 2.6.21 that between the bug report on March 31th and the
> release of 2.6.21 on April 21th, noone started debugging this bug. [3] [4]
>
> > > And look e.g. at the many (and non-trivial) changes between -rc7 and
> > > -final, resulting in more than one report from people who were running
> > > -rc7 without problems - and 2.6.21 doesn't work for them.
> >
> > I agree that's unfortunate.
> >
> > > It's not a choice between "regressions don't matter" and "no
> regressions",
> > > it's about the place in the area between these two extremes. I have my
> > > opinions on what I want to expect from a stable Linux kernel, and other
> > > people have different opinins.
> >
> > Everyone is going to disagree to some extent; and their own comfort
> > zone. So a certain amount compromise is always going to be necessary.
> > Of course, it's up to you decide whether this has gone beyond the zone
> > where you aren't comfortable working with other people's development
> > style.
> >
> > Regards,
> >
> > - Ted
>
> cu
> Adrian
>
> [1] http://lkml.org/lkml/2007/4/26/2
> [2] http://lkml.org/lkml/2007/4/25/496
> [3] http://lkml.org/lkml/2007/4/26/496
> [4] and although it turned out this specific regression was already
> fixed in 2.6.21, I hope you get my point
>
> --
>
> "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@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>

--
Markus Rechberger