All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Goodwin <markgw@sgi.com>
To: Richard Ems <Richard.Ems@cape-horn-eng.com>
Cc: Russell Cattelan <cattelan@thebarn.com>,
	xfs@oss.sgi.com, Bill O'Donnell <billodo@sgi.com>
Subject: Re: XFS internal error xfs_btree_check_lblock
Date: Tue, 22 Jul 2008 21:27:33 +1000	[thread overview]
Message-ID: <4885C425.9020309@sgi.com> (raw)
In-Reply-To: <4885BB2E.3010508@cape-horn-eng.com>



Richard Ems wrote:
> Mark Goodwin wrote:
>> Some of the above might not refer directly to the final committed
>> patches but the thread URLs should be accurate. These are bug fixes
>> that go a long way back and really do need to be back-ported and
>> pushed out for the mentioned distros. There are probably other patches
>> not listed above that should be considered too.
>
> Hi Mark, thanks for the list and clarifications.
>
> But still some more questions ... who does the backporting for the
> distros? SGI or the distros themselves?

Generally the distros, except for SGI storage platforms and SLES where
SGI has a contractural support agreement with Novell.

> Is someone from Novell / SUSE / openSUSE reading here?

Andreas Gruenbacher is probably listening

> When can we *expect* to have these patches backported? In one month?
> Three months? More?

For SLES, within a week. For OpenSuSE presumeably the SLES folks will
follow-up with OpenSuSE, but I can't predict when. For Fedora, Eric
Sandeen.  For RHEL (on anything except SGI storage platforms), nobody
since XFS is not supported directly by Redhat. For all other distros
and server & NAS vendors, it's entirely up to their maintainers and
respective support organization - generally they track a release or
two behind kernel.org.

Cheers

-- 

  Mark Goodwin                                  markgw@sgi.com
  Engineering Manager for XFS and PCP    Phone: +61-3-99631937
  SGI Australian Software Group           Cell: +61-4-18969583
-------------------------------------------------------------

  reply	other threads:[~2008-07-22 11:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-18 14:55 XFS internal error xfs_btree_check_lblock Richard Ems
2008-07-19  3:08 ` Mark Goodwin
2008-07-19 16:36   ` sandeen
2008-07-21  9:33   ` Richard Ems
2008-07-21 16:11     ` Eric Sandeen
2008-07-21 23:40       ` Mark Goodwin
2008-07-22  2:07         ` Eric Sandeen
2008-07-21 16:06   ` Russell Cattelan
2008-07-22  3:24     ` Mark Goodwin
2008-07-22 10:49       ` Richard Ems
2008-07-22 11:27         ` Mark Goodwin [this message]
2008-07-22 15:22           ` Eric Sandeen

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=4885C425.9020309@sgi.com \
    --to=markgw@sgi.com \
    --cc=Richard.Ems@cape-horn-eng.com \
    --cc=billodo@sgi.com \
    --cc=cattelan@thebarn.com \
    --cc=xfs@oss.sgi.com \
    /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.