On Tue, Nov 22, 2016 at 08:36:35PM -0800, Darrick J. Wong wrote: > ocfs2_dio_end_io_write eats whatever errors may happen, > which means that write errors do not propagate to userspace. > Fix that. Btw, can you also fix up the ocfs2 calling conventions for ->end_io so that it also does the unlock for the error case in ocfs2_dio_end_io? I looked at all the inode locking in ocfs2, but couldn't convince me that either the current code nor the version with the locking changed is correct.. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
