From: Christoph Hellwig <hch@infradead.org>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
Cc: xfs@oss.sgi.com
Subject: Re: XFS: accounting of reclaimable inodes is incorrect
Date: Tue, 7 Jun 2011 10:09:49 -0400 [thread overview]
Message-ID: <20110607140949.GA31769@infradead.org> (raw)
In-Reply-To: <4DEE2C36.8030008@profihost.ag>
On Tue, Jun 07, 2011 at 03:48:38PM +0200, Stefan Priebe - Profihost AG wrote:
> Am 07.06.2011 15:34, schrieb Christoph Hellwig:
> >On Tue, Jun 07, 2011 at 02:58:32PM +0200, Stefan Priebe - Profihost AG wrote:
> >Linux 2.6.32 isn't really something supported by us. It's not just a
> >very old codebase, but also one where a lot of the XFS code was pretty
> >much in flux. If you want supported old releases work use one of
> >the commercially supported one like RedHat or SuSE.
> OK so my thought was totally wrong. I thought the longterm stable
> releases will still get bugfixed by SGI or whoever wrote the stuff.
> Sorry for that then. But what is then the idea of a longterm stable?
I have no idea what the idea is, but it's clearly not viable for normal
kernel developers. Backporting code to age old releases and QAing it is
a major effort, and people generally don't do it unless they are paid
for it.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-06-07 14:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-07 11:42 XFS: accounting of reclaimable inodes is incorrect Stefan Priebe - Profihost AG
2011-06-07 11:54 ` Christoph Hellwig
2011-06-07 12:58 ` Stefan Priebe - Profihost AG
2011-06-07 13:34 ` Christoph Hellwig
2011-06-07 13:48 ` Stefan Priebe - Profihost AG
2011-06-07 14:09 ` Christoph Hellwig [this message]
2011-06-07 14:00 ` Dave Howorth
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=20110607140949.GA31769@infradead.org \
--to=hch@infradead.org \
--cc=s.priebe@profihost.ag \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox