| To: | Suzuki <suzuki@xxxxxxxxxx> |
|---|---|
| Subject: | Re: [RFC] Badness in __mutex_unlock_slowpath with XFS stress tests |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Thu, 9 Mar 2006 12:03:06 +0000 |
| Cc: | linux-fsdevel@xxxxxxxxxxxxxxx, "linux-aio kvack.org" <linux-aio@xxxxxxxxx>, lkml <linux-kernel@xxxxxxxxxxxxxxx>, suparna <suparna@xxxxxxxxxx>, akpm@xxxxxxxx, linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <440FDF3E.8060400@in.ibm.com> |
| Mail-followup-to: | Christoph Hellwig <hch@xxxxxxxxxxxxx>, Suzuki <suzuki@xxxxxxxxxx>, linux-fsdevel@xxxxxxxxxxxxxxx, "linux-aio kvack.org" <linux-aio@xxxxxxxxx>, lkml <linux-kernel@xxxxxxxxxxxxxxx>, suparna <suparna@xxxxxxxxxx>, akpm@xxxxxxxx, linux-xfs@xxxxxxxxxxx |
| References: | <440FDF3E.8060400@in.ibm.com> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.4.2.1i |
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. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | TAKE 950678 - XFSQA: Ass fail (ifp->if_flags & (0x02|0x08)) == 0x02, xfs_bmap.c, line: 3448, Mandy Miklos |
|---|---|
| Next by Date: | Re: [RFC] Badness in __mutex_unlock_slowpath with XFS stress tests, Nathan Scott |
| Previous by Thread: | TAKE 950678 - XFSQA: Ass fail (ifp->if_flags & (0x02|0x08)) == 0x02, xfs_bmap.c, line: 3448, Mandy Miklos |
| Next by Thread: | Re: [RFC] Badness in __mutex_unlock_slowpath with XFS stress tests, Nathan Scott |
| Indexes: | [Date] [Thread] [Top] [All Lists] |