2007-05-23 11:03:09

by Vincent Fortier

[permalink] [raw]
Subject: RE: [stable] [patch 00/69] -stable review

> -----Message d'origine-----
> De : Greg KH [mailto:[email protected]]
> Envoy? : 22 mai 2007 23:37
> ? : Fortier,Vincent [Montreal]
>
> On Tue, May 22, 2007 at 09:28:34PM -0400, Fortier,Vincent
> [Montreal] wrote:
> > > -----Message d'origine-----
> > > De : [email protected]
> > > [mailto:[email protected]] De la part de Chuck
> > > Ebbert Envoy? : 21 mai 2007 18:24
> > >
> > > Adrian Bunk wrote:
> > > > On Mon, May 21, 2007 at 12:31:48PM -0700, Andrew Morton wrote:
> > > >> On Mon, 21 May 2007 12:16:12 -0700 Chris Wright
> > > >> <[email protected]> wrote:
> > > >>
> > > >>> This is the start of the stable review cycle for the 2.6.21.2 release.
> > > >> Gee a lot of these are fixing recently-added regressions :( ...
> > > >
> > > > If only it would fix all of them...
> > > >
> > > > Michal's list [1] currently contains 51 different regressions in
> > > > 2.6.21 compared to 2.6.20 (12 of them were already reported before
> > > > 2.6.21 was released).
> > >
> > > Yeah, 2.6.21 seems awfully buggy, and patches to fix many of the
> > > bugs haven't appeared.
> > >
> > > Another 2.6.20 update seems to be in order...
> >
> > Hi,
> >
> > If there is a new stable 2.6.20 / 2.6.21, would it be
> possible that they both contain also this patch to keep the
> same behaviour between 2.6.20 -> 2.6.22 kernels regarding
> paravirt_ops GPL export?
> >
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=com
> > mit;h=21564fd2a3deb48200b595332f9ed4c9f311f2a7
>
> Why? Is there an in-kernel use for that export?

I sincerely dont know... Although:
- * NOTE: CONFIG_PARAVIRT is experimental and the paravirt_ops
- * semantics are subject to change. Hence we only do this
- * internal-only export of this, until it gets sorted out and
- * all lowlevel CPU ops used by modules are separately exported.

Makes me think there was a "good enough" reason to export instead of export GPL and that it "could" be usefull to keep the same behaviour for that same experimental feature under 2.6.20 / 2.6.21. Although, the "until it gets sorted out" makes me think it might planned to get removed before the end of 2.6.22

Thnx.

- vin


2007-05-23 15:15:10

by Greg KH

[permalink] [raw]
Subject: Re: [stable] [patch 00/69] -stable review

On Wed, May 23, 2007 at 07:02:29AM -0400, Fortier,Vincent [Montreal] wrote:
> > -----Message d'origine-----
> > De : Greg KH [mailto:[email protected]]
> > Envoy? : 22 mai 2007 23:37
> > ? : Fortier,Vincent [Montreal]
> >
> > On Tue, May 22, 2007 at 09:28:34PM -0400, Fortier,Vincent
> > [Montreal] wrote:
> > > > -----Message d'origine-----
> > > > De : [email protected]
> > > > [mailto:[email protected]] De la part de Chuck
> > > > Ebbert Envoy? : 21 mai 2007 18:24
> > > >
> > > > Adrian Bunk wrote:
> > > > > On Mon, May 21, 2007 at 12:31:48PM -0700, Andrew Morton wrote:
> > > > >> On Mon, 21 May 2007 12:16:12 -0700 Chris Wright
> > > > >> <[email protected]> wrote:
> > > > >>
> > > > >>> This is the start of the stable review cycle for the 2.6.21.2 release.
> > > > >> Gee a lot of these are fixing recently-added regressions :( ...
> > > > >
> > > > > If only it would fix all of them...
> > > > >
> > > > > Michal's list [1] currently contains 51 different regressions in
> > > > > 2.6.21 compared to 2.6.20 (12 of them were already reported before
> > > > > 2.6.21 was released).
> > > >
> > > > Yeah, 2.6.21 seems awfully buggy, and patches to fix many of the
> > > > bugs haven't appeared.
> > > >
> > > > Another 2.6.20 update seems to be in order...
> > >
> > > Hi,
> > >
> > > If there is a new stable 2.6.20 / 2.6.21, would it be
> > possible that they both contain also this patch to keep the
> > same behaviour between 2.6.20 -> 2.6.22 kernels regarding
> > paravirt_ops GPL export?
> > >
> > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=com
> > > mit;h=21564fd2a3deb48200b595332f9ed4c9f311f2a7
> >
> > Why? Is there an in-kernel use for that export?
>
> I sincerely dont know... Although:

Then I'd prefer to not make this change to the -stable tree :)

thanks,

greg k-h