From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [RFC] Badness in __mutex_unlock_slowpath with XFS stress tests Date: Thu, 9 Mar 2006 12:03:06 +0000 Message-ID: <20060309120306.GA26682@infradead.org> References: <440FDF3E.8060400@in.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-fsdevel@vger.kernel.org, "linux-aio kvack.org" , lkml , suparna , akpm@osdl.org, linux-xfs@oss.sgi.com Return-path: To: Suzuki Content-Disposition: inline In-Reply-To: <440FDF3E.8060400@in.ibm.com> Sender: owner-linux-aio@kvack.org List-Id: linux-fsdevel.vger.kernel.org On Thu, Mar 09, 2006 at 01:24:38PM +0530, Suzuki wrote: > > Missed out linux-aio & linux-fs-devel lists. Forwarding. > > Comments ? I've seen this too. The problem is that __generic_file_aio_read can return with or without the i_mutex locked in the direct I/O case for filesystems that set DIO_OWN_LOCKING. It's a nasty one and I haven't found a better solution than copying lots of code from filemap.c into xfs. -- To unsubscribe, send a message with 'unsubscribe linux-aio' in the body to majordomo@kvack.org. For more info on Linux AIO, see: http://www.kvack.org/aio/ Don't email: aart@kvack.org