On Thu, Apr 05, 2012 at 10:35:40AM -0600, Orion Poplawski wrote: > On 03/29/2012 03:17 PM, Dr James Bruce Fields wrote: > >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. > > So, is this all set to eventually make it into the mainline kernel? > Or is there still something I can do to help move it along? If you could confirm whether the patch in http://www.spinics.net/lists/linux-nfs/msg28840.html fixes your problem, that would help. --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
