Nathan Scott 3fb962bde4 Fix a direct I/O locking issue revealed by the new mutex code.
Affects only XFS (i.e. DIO_OWN_LOCKING case) - currently it is
not possible to get i_mutex locking correct when using DIO_OWN
direct I/O locking in a filesystem due to indeterminism in the
possible return code/lock/unlock combinations.  This can cause
a direct read to attempt a double i_mutex unlock inside XFS.

We're now ensuring __blockdev_direct_IO always exits with the
inode i_mutex (still) held for a direct reader.

Tested with the three different locking modes (via direct block
device access, ext3 and XFS) - both reading and writing; cannot
find any regressions resulting from this change, and it clearly
fixes the mutex_unlock warning originally reported here:
http://marc.theaimsgroup.com/?l=linux-kernel&m=114189068126253&w=2

Signed-off-by: Nathan Scott <nathans@sgi.com>
Acked-by: Christoph Hellwig <hch@lst.de>
2006-03-15 15:14:45 +11:00
..
2006-01-11 18:42:13 -08:00
2006-01-14 18:25:19 -08:00
2005-11-08 16:54:53 +01:00
2005-10-04 13:22:01 -07:00
2006-02-17 13:59:26 -08:00
2006-01-18 19:20:23 -08:00
2006-03-09 19:47:37 -08:00
2006-01-11 18:42:13 -08:00
2005-11-07 07:54:06 -08:00
2006-03-06 18:40:45 -08:00
2006-02-01 08:53:09 -08:00
2006-01-11 18:42:13 -08:00
2006-02-03 08:32:04 -08:00
2006-01-08 20:13:48 -08:00
2006-01-11 18:42:13 -08:00
2006-01-10 08:01:25 -08:00
2006-01-31 15:24:34 +01:00
2006-03-08 16:46:08 -08:00
2006-02-17 13:59:28 -08:00
2006-03-08 14:14:01 -08:00
2006-01-11 18:42:13 -08:00
2006-01-11 18:42:13 -08:00
2006-01-08 20:12:40 -08:00
2006-03-07 09:16:35 -08:00
2006-03-08 14:14:01 -08:00
2005-10-30 17:37:32 -08:00
2006-01-11 18:42:13 -08:00
2006-01-11 18:42:13 -08:00
2006-02-03 08:32:11 -08:00
2006-01-18 19:20:30 -08:00
2006-01-18 19:20:29 -08:00
2006-03-08 14:03:09 -08:00
2006-01-08 20:13:56 -08:00
2005-11-07 18:18:11 -08:00
2006-01-11 18:42:13 -08:00
2006-02-17 13:59:28 -08:00
2006-02-11 21:41:10 -08:00
2006-02-22 09:39:02 -08:00