On Thu, Mar 29, 2012 at 05:08:38PM -0400, Dr James Bruce Fields wrote: > Anyway, something like the following (untested) should change v3 to > return nfs_ok in this case, and v4 to return the same errors it would on > a non-create open. Looking at the history, I think the v3 behavior has been there from the start. I wonder why we've never gotten a bug report? Looking at wireshark.... I guess the client always does a lookup first, so we never hit this case (unless someone replaces the file by a non-regular-file between a lookup and a create?) --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
