On Fri, Feb 20, 2015 at 8:19 AM, Christoph Hellwig <hch@xxxxxxxxxxxxx> wrote: > On Fri, Feb 20, 2015 at 08:16:25AM -0800, Trond Myklebust wrote: >> NFS: struct nfs_commit_info.lock must always point to inode->i_lock > > Is there any point in even keeping that lock pointer around then? We either have to pass a pointer to the lock or to the inode itself. I'm fine with either, but I figured the more conservative option would be keeping what we have now. -- Trond Myklebust Linux NFS client maintainer, PrimaryData trond.myklebust@xxxxxxxxxxxxxxx -- 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
