All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Theodore Tso <tytso@MIT.EDU>
Cc: 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 10:03:38 +0100	[thread overview]
Message-ID: <20110608100338.66a98328@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <C4F797E7-3B2F-4BAD-BF69-2182DEA775A5@mit.edu>

> > 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.

It's often not that simple. As vendor trees diverge you may find it's not
a case of 'sending patch X upstream' because the patches you need may
well depend upon other things in the vendor tree not all of which will be
in the 'stable' tree. So it's a base at best.

> Not all distributions will participate in the maintenance stable tree.  Red Hat for example is probably worried about people  (specifically, Oracle) taking their kernel expertise "for free" and bidding it against them.

Judging from the commit log that isn't the case.

Besides which I hear a rumour that oracle employees have learned how to
download files from other websites and look at the content so it won't
make any odds 8)

Alan

  parent reply	other threads:[~2011-06-08  9:01 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
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 [this message]
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=20110608100338.66a98328@lxorguk.ukuu.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=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.