Messages in this thread | | | Date | Thu, 9 Mar 2006 22:42:19 +0000 | From | Christoph Hellwig <> | Subject | Re: [RFC] Badness in __mutex_unlock_slowpath with XFS stress tests |
| |
On Fri, Mar 10, 2006 at 09:30:42AM +1100, Nathan Scott wrote: > Not for reads AFAICT - __generic_file_aio_read + own-locking > should always have released i_mutex at the end of the direct > read - are you thinking of writes or have I missed something?
if an error occurs before a_ops->direct_IO is called __generic_file_aio_read will return with i_mutex still locked. Note that checking for negative return values is not enough as __blockdev_direct_IO can return errors aswell.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |