From: david@lang.hm
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
Cc: Theodore Tso <tytso@MIT.EDU>, linux-kernel@vger.kernel.org
Subject: Re: XFS problem in 2.6.32
Date: Tue, 7 Jun 2011 12:45:15 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1106071239530.28905@asgard.lang.hm> (raw)
In-Reply-To: <4DEE2C70.8060301@profihost.ag>
On Tue, 7 Jun 2011, Stefan Priebe - Profihost AG wrote:
> Date: Tue, 07 Jun 2011 15:49:36 +0200
>>> So who keeps track on which patches needs to get backported or not? And
>>> who will backport XFS fixes back to 2.6.32?
>>
>> An interested kernel developer. They can become interested because they
>> personally have the time or interest, or because someone pays them to
>> become interested. Support of the stable kernel series is not something
>> that happens magically, or which is funded by a charity, you know. That's
>> why some companies pay $$$ for a supported distribution kernel.
> OK so my thought was totally wrong. I thought the longterm stable releases
> will still get bugfixed by SGI or whoever wrote the stuff. Sorry for that
> then. But what is then the idea of a longterm stable?
development and bugfixes are done on the latest kernel, if the problem is
known to affect old kernels the developers sometimes remember to notify
the -stable list that this patch is important and needs to be applied to
older kernels.
whoever the maintainer of the -stable/-longterm tree is (be it an
individual or a team employeed by some comapny) then looks at the patch
and considers backporting it (if it's too hard, or to intrusive, they may
decide not to).
the idea of the lonterm kernels is that organizations need to maintain a
kernel for a long time due to commitments that they have made (Debian
doesn't want to change the kernel it ships in a stable version, RedHat
doesn't want to change the kernel version in a RHEL release, etc), and so
they publicly announce this so that anyone else wanting to use the same
kernel version can share in the work (and therefor everyone can benifit
from each other's work)
David Lang
next prev parent reply other threads:[~2011-06-07 19:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-07 12:46 XFS problem in 2.6.32 Stefan Priebe - Profihost AG
2011-06-07 13:36 ` Theodore Tso
2011-06-07 13:49 ` Stefan Priebe - Profihost AG
2011-06-07 19:45 ` david [this message]
2011-06-07 21:57 ` Stefan Priebe - Profihost AG
2011-06-07 22:05 ` david
2011-06-08 3:28 ` Theodore Tso
2011-06-08 7:05 ` Stefan Priebe - Profihost AG
2011-06-08 8:00 ` John Kacur
2011-06-08 13:38 ` Ted Ts'o
2011-06-08 14:16 ` Mike Snitzer
2011-06-08 18:50 ` Ted Ts'o
2011-06-08 21:01 ` Christoph Hellwig
2011-06-08 9:03 ` Alan Cox
2011-06-08 13:30 ` Steven Rostedt
2011-06-09 2:57 ` Dave Chinner
2011-06-09 7:22 ` Stefan Priebe - Profihost AG
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=alpine.DEB.2.02.1106071239530.28905@asgard.lang.hm \
--to=david@lang.hm \
--cc=linux-kernel@vger.kernel.org \
--cc=s.priebe@profihost.ag \
--cc=tytso@MIT.EDU \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.