On Wed, Jan 14, 2015 at 10:09:03PM +0800, Peng Tao wrote: > Running xfstest generic/036, we'll get following VM_BUG_ON in > nfs_direct_IO(). 036 toggles O_DIRECT flag while IO is going on. > So the VM_BUG_ON should not exist there. However, we have a deadlock > in the code path as well, because inode->i_mutex is taken when calling > into ->direct_IO. And nfs_file_direct_write() would grab inode->i_mutex > again. > > Meanwhile, nfs_file_direct_write() does a lot of things that is already > done by vfs before ->direct_IO is called. So skip those duplicates. One > exception is i_size_write. vfs does not take i_lock when setting i_size. > But nfs appears to need i_lock when setting i_size. But given that NFS implements direct I/O without ->direct_IO (except for the horrible swap over NFS hack that is on it's way out) it shold never be called. The right fix is to determine the O_DIRECT flag in one place when entering a write, and then pass it down on the stack. We already do this in XFS for example, it just needs to be expanded to filemap.c so that more filesystems benefit from it. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
