public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: Greg KH <greg@kroah.com>,
	stable@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [stable] -longterm kernels (Was: Re: Patch Upstream: iwlwifi: fix skb usage after free)
Date: Thu, 5 May 2011 17:17:02 +0200	[thread overview]
Message-ID: <20110505151702.GG2090@1wt.eu> (raw)
In-Reply-To: <20110505145854.GA4670@redhat.com>

Hi,

On Thu, May 05, 2011 at 04:58:55PM +0200, Stanislaw Gruszka wrote:
> BTW, Greg, perhaps -logterm releasing policy should be revised somehow.
> Currently we have .32, .33, .34, .35 -longterm, what is kind a much. If
> I could suggest something, would be nice to have longterm chosen
> versions predictable and constants i.e. one from every 3 kernel
> releases, like .35, .38, .41 ... . That would make distributions, that
> try to do release every half year very happy, because they will know
> what kernel to choose, which will be widely supported and tested.

Longterm kernels are maintained on a voluntary basis, which explains
there is no rule. We had 2.6.16, 2.6.27 and now 2.6.32 which were
initially announced as longterm supported. When Greg announced dropping
2.6.27, I proposed to take it over because I have some uses for it and
I know other people who rely on it. Most likely for very similar reasons
Paul and Andi volunteered to maintain 2.6.34 and 2.6.35 alive.

I agree it would be much easier for everyone if all longterm kernels were
announced early. Still there are a lot of users who can't easily upgrade
for whatever reason and who are happy with someone keeping their kernel
updated. I tend to consider that Greg's kernels are more "official" than
other ones, and if some backporting must be done by patch authors, I think
it should be for these kernels first. Also, .32 is not that far away from
the 3 other longterm kernels, so when a developer writes a .32 backport,
chances are that adaptations will not be too hard for the 3 other ones.

> Also
> developers will have a bit less work with backporting fixes, as having
> same bug in n and n-3 release is less probable, than having the same bug
> in n and n-1.

While less probable, I'm still amazed by the number of fixes from -master
that still apply to 2.6.27, and sometimes (but to a less extent) even to
2.4.37 ! The fact that fixes and regressions span that many kernel versions
probably is one of the reasons there is demand for longterm kernels.

Just my 2 cents,
Willy


  reply	other threads:[~2011-05-05 15:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201105030110.p431A5W0005426@hera.kernel.org>
     [not found] ` <20110504223605.GA5967@kroah.com>
2011-05-05 14:58   ` -longterm kernels (Was: Re: [stable] Patch Upstream: iwlwifi: fix skb usage after free) Stanislaw Gruszka
2011-05-05 15:17     ` Willy Tarreau [this message]
2011-05-05 15:25     ` Greg KH
2011-05-07 14:55       ` -longterm kernels Stanislaw Gruszka
2011-05-07 15:40         ` Greg KH
2011-05-07 15:57           ` Stanislaw Gruszka
2011-05-07 19:01             ` Greg KH
2011-05-09  9:18               ` Stanislaw Gruszka
2011-05-08  5:09         ` Mike Galbraith

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=20110505151702.GG2090@1wt.eu \
    --to=w@1wt.eu \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sgruszka@redhat.com \
    --cc=stable@kernel.org \
    /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