On Mon, Feb 19, 2007 at 11:58:16PM +0300, Ananiev, Leonid I wrote: > > while triggering EIO in invalidate_inode_pages2_range() > ... > > With this patch aio-stress sees -EIO. > > Actually if invalidate_inode_pages2_range() returns EIO it means > that internal kernel synchronization conflict was happen. > It is reported to user as hardware IO error. > Iteration in synchronization process could be performed instead. >
aio is not responsible for this particular synchronization. Those fixes (if we make them) should come from other places. The patch is important to get aio error handling right. I would argue that one common cause of the EIO is userland error (mmap concurrent with O_DIRECT), and EIO is the correct answer. -chris - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
