From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: XFS: accounting of reclaimable inodes is incorrect
Date: Tue, 07 Jun 2011 15:48:38 +0200 [thread overview]
Message-ID: <4DEE2C36.8030008@profihost.ag> (raw)
In-Reply-To: <20110607133429.GA9049@infradead.org>
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?
>> Redhat seems to have fixed it on it's own:
>> https://bugzilla.redhat.com/show_bug.cgi?id=642680
>
> I suspect the upstream commit you want is
> 081003fff467ea0e727f66d5d435b4f473a789b3, but I can't gurantee this
> actually applies to the 2.6.32 codebase.
No it doesn't. I already tried to implement it into current 2.6.32.41 code.
Greets Stefan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-06-07 13:48 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 [this message]
2011-06-07 14:09 ` Christoph Hellwig
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=4DEE2C36.8030008@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=hch@infradead.org \
--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.