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 07:54:42 -0400 [thread overview]
Message-ID: <20110607115441.GA4653@infradead.org> (raw)
In-Reply-To: <4DEE0EA4.9090002@profihost.ag>
On Tue, Jun 07, 2011 at 01:42:28PM +0200, Stefan Priebe - Profihost AG wrote:
> Hi,
>
> it seems that a bug was backported into the latest 2.6.32 longterm
> stable kernel. Now the patch "XFS: accounting of reclaimable inodes
> is incorrect" needs to get backported to 2.6.32.
>
> Who can help? Who is responsible?
For -stable releases no one really is. If you want to help you can
backport it and send it to the stable mailinglist.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-06-07 11:54 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 [this message]
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
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=20110607115441.GA4653@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