From mboxrd@z Thu Jan  1 00:00:00 1970
From: Nick Piggin <npiggin@kernel.dk>
Subject: Re: [PATCH 17/21] fs: protect wake_up_inode with inode->i_lock
Date: Fri, 22 Oct 2010 00:16:02 +1100
Message-ID: <20101021131602.GA13620@amd>
References: <1287622186-1935-1-git-send-email-david@fromorbit.com>
 <1287622186-1935-18-git-send-email-david@fromorbit.com>
 <20101021021722.GB5241@infradead.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: Dave Chinner <david@fromorbit.com>, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org
To: Christoph Hellwig <hch@infradead.org>
Return-path: <linux-kernel-owner@vger.kernel.org>
Content-Disposition: inline
In-Reply-To: <20101021021722.GB5241@infradead.org>
Sender: linux-kernel-owner@vger.kernel.org
List-Id: linux-fsdevel.vger.kernel.org

On Wed, Oct 20, 2010 at 10:17:22PM -0400, Christoph Hellwig wrote:
> Looks good, and thanks for documenting unlock_new_inode.

You wanted an example of how the irregular locking requires
handling of new concurrency situations? This is another good
one.