From mboxrd@z Thu Jan  1 00:00:00 1970
From: Christoph Hellwig <hch@infradead.org>
Subject: Re: inconsistent lock state (xfs)
Date: Fri, 10 Dec 2010 15:58:52 -0500
Message-ID: <20101210205852.GA3086@infradead.org>
References: <814FDEDC-D26A-4EDB-843C-5C8EDE2A4C61@oracle.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: linux-fsdevel@vger.kernel.org
To: Chuck Lever <chuck.lever@oracle.com>
Return-path: <linux-fsdevel-owner@vger.kernel.org>
Received: from bombadil.infradead.org ([18.85.46.34]:37426 "EHLO
	bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1756822Ab0LJU6x (ORCPT
	<rfc822;linux-fsdevel@vger.kernel.org>);
	Fri, 10 Dec 2010 15:58:53 -0500
Content-Disposition: inline
In-Reply-To: <814FDEDC-D26A-4EDB-843C-5C8EDE2A4C61@oracle.com>
Sender: linux-fsdevel-owner@vger.kernel.org
List-ID: <linux-fsdevel.vger.kernel.org>

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.