From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: david@lang.hm
Cc: Theodore Tso <tytso@MIT.EDU>, linux-kernel@vger.kernel.org
Subject: Re: XFS problem in 2.6.32
Date: Tue, 07 Jun 2011 23:57:46 +0200 [thread overview]
Message-ID: <4DEE9EDA.90001@profihost.ag> (raw)
In-Reply-To: <alpine.DEB.2.02.1106071239530.28905@asgard.lang.hm>
> 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).
So i have to contact Greg Kohan from SUSE directly?
> 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)
That was what i thoght. So a bug like this should get fixed right?
Otherwise this makes no sense. Sadly Redhat has ported the fix back in
his RHEL 6 2.6.32 kernel but they haven't send the patch to stable /
vanilla team.
Stefan
next prev parent reply other threads:[~2011-06-07 21:57 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
2011-06-07 21:57 ` Stefan Priebe - Profihost AG [this message]
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=4DEE9EDA.90001@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=david@lang.hm \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox