[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110608210125.GA8208@infradead.org>
Date: Wed, 8 Jun 2011 17:01:25 -0400
From: Christoph Hellwig <hch@...radead.org>
To: Ted Ts'o <tytso@....edu>, Mike Snitzer <snitzer@...hat.com>,
John Kacur <jkacur@...hat.com>,
Stefan Priebe - Profihost AG <s.priebe@...fihost.ag>,
david@...g.hm, linux-kernel@...r.kernel.org
Subject: Re: XFS problem in 2.6.32
On Wed, Jun 08, 2011 at 02:50:16PM -0400, Ted Ts'o wrote:
> On Wed, Jun 08, 2011 at 10:16:59AM -0400, Mike Snitzer wrote:
> >
> > And what _exactly_ is Red Hat (not) doing? Red Hat isn't going crazy
> > backporting its upstream > 2.6.32 fixes to 2.6.32.y even when Red Hat
> > doesn't consume 2.6.32.y? *gasp*
>
> Well, the original poster was expecting that (unspecified people)
> would be doing this regularly (in fact he was complaining about how an
> XFS bug fixed in RHEL wasn't fixed in 2.6.32.y). I was explaining how
> it wasn't happening, and it was perfectly acceptable for that to be
> the case.
>
> So I was actually *defending* Red Hat....
Btw, Redhat has a completely different XFS codebase than mainline
2.6.32, here's the diffstat summary between 2.6.32 and rhel6.1:
96 files changed, 5083 insertions(+), 5211 deletions(-)
Which roughly equals the diff between 2.6.32 and 2.6.34. So there's
a fairly large chance things simply won't apply as-is anyway. The same
is also true for ext4, btrfs and nfs.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists