From: Christoph Hellwig <hch@infradead.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: inconsistent lock state (xfs)
Date: Fri, 10 Dec 2010 15:58:52 -0500 [thread overview]
Message-ID: <20101210205852.GA3086@infradead.org> (raw)
In-Reply-To: <814FDEDC-D26A-4EDB-843C-5C8EDE2A4C61@oracle.com>
On Fri, Dec 10, 2010 at 02:40:06PM -0500, Chuck Lever wrote:
> Seen during a Linux kernel build (make -s -j3 all) on a two-processor VMware guest.
Yes, it's pretty common. Except for an obscure ioctl it's a false
positive. The patch titled:
[PATCH, RFC] prune back iprune_sem
I sent a while ago fixes it.
prev parent reply other threads:[~2010-12-10 20:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-10 19:40 inconsistent lock state (xfs) Chuck Lever
2010-12-10 20:58 ` Christoph Hellwig [this message]
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=20101210205852.GA3086@infradead.org \
--to=hch@infradead.org \
--cc=chuck.lever@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).