From: Theodore Tso <tytso@MIT.EDU>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
Cc: linux-kernel@vger.kernel.org
Subject: Re: XFS problem in 2.6.32
Date: Tue, 7 Jun 2011 09:36:41 -0400 [thread overview]
Message-ID: <6D8DA3D2-D90B-4D82-BDC9-C3F0264A68BF@mit.edu> (raw)
In-Reply-To: <4DEE1D96.6020208@profihost.ag>
On Jun 7, 2011, at 8:46 AM, Stefan Priebe - Profihost AG wrote:
> Hi List,
>
> i've massive problems with a machine using 2.6.32 kernel and XFS: I've desribed the problem here:
> http://www.spinics.net/lists/xfs/msg04984.html
>
> The reply on the XFS mailinglist was:
> http://www.spinics.net/lists/xfs/msg04994.html
>
> 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.
-- Ted
next prev parent reply other threads:[~2011-06-07 13:36 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 [this message]
2011-06-07 13:49 ` Stefan Priebe - Profihost AG
2011-06-07 19:45 ` david
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=6D8DA3D2-D90B-4D82-BDC9-C3F0264A68BF@mit.edu \
--to=tytso@mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=s.priebe@profihost.ag \
/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.