mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: "Ted Ts'o" <tytso@mit.edu>, Mike Snitzer <snitzer@redhat.com>,
	John Kacur <jkacur@redhat.com>,
	Stefan Priebe - Profihost AG <s.priebe@profihost.ag>,
	david@lang.hm, linux-kernel@vger.kernel.org
Subject: Re: XFS problem in 2.6.32
Date: Wed, 8 Jun 2011 17:01:25 -0400	[thread overview]
Message-ID: <20110608210125.GA8208@infradead.org> (raw)
In-Reply-To: <20110608185016.GI30037@thunk.org>

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.


  reply	other threads:[~2011-06-08 21:01 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-07 12:46 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
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 [this message]
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=20110608210125.GA8208@infradead.org \
    --to=hch@infradead.org \
    --cc=david@lang.hm \
    --cc=jkacur@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=s.priebe@profihost.ag \
    --cc=snitzer@redhat.com \
    --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

Powered by JetHome