Marc Eshel points out that an NFSv4 LOCKT call is handled without calling any ->lock() method on the underlying filesystem. The problem is that NFSv4's LOCKT is really a inode method--it takes a filehandle, not a stateid, as an argument. The current code hacks around this by using a one-off struct file with only the dentry field initialized. So the simple fix is to initialize the file operations as well. But the original hack makes me a little nervous, so I'm inclined to just do a temporary open instead. Objections? --b. -- 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
