From: Christoph Hellwig <hch@infradead.org>
To: Christian Kujau <lists@nerdbynature.de>
Cc: xfs@oss.sgi.com
Subject: Re: 3.5.0-rc5: inconsistent lock state
Date: Thu, 5 Jul 2012 03:43:07 -0400 [thread overview]
Message-ID: <20120705074307.GA28127@infradead.org> (raw)
In-Reply-To: <alpine.DEB.2.01.1207041206390.5568@trent.utfs.org>
On Wed, Jul 04, 2012 at 12:13:32PM -0700, Christian Kujau wrote:
> Hi,
>
> this powerpc machine is running 3.5.0-rc5 for 2 days now and this happened
> today:
See my "do not take the iolock in inode reclaim context" series from
yesterday, which should take care of this.
Btw, if you hit this it's a sign you have out of the inode attributes,
so if this isn't just a single inode with them you might be better off
using larger inodes.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-07-05 7:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-04 19:13 3.5.0-rc5: inconsistent lock state Christian Kujau
2012-07-04 19:14 ` Christian Kujau
2012-07-05 7:43 ` Christoph Hellwig [this message]
2012-07-05 12:44 ` Christian Kujau
2012-07-05 21:59 ` Dave Chinner
2012-07-05 23:39 ` Christian Kujau
2012-07-06 1:01 ` Dave Chinner
2012-07-06 1:55 ` Christian Kujau
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=20120705074307.GA28127@infradead.org \
--to=hch@infradead.org \
--cc=lists@nerdbynature.de \
--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