On Thu, Jul 16, 2009 at 02:25:29PM -0500, Tom Haynes wrote: > J. Bruce Fields wrote: >> I don't see how it could be a problem for the client to try an >> unadvertised flavor. The server has to enforce the choice of flavor >> anyway. >> > > Yes, the server needs to enforce it, but why is the client trying a > flavor that the server > says it does not support? Could just be excessively persistent of optimistic. (Or in this case probably it just doesn't have any negotiation code, so it's simplest just to try the one flavor that was specified on the mount; seems fair to me.) There's also cases where this could also happen just due to bad timing: maybe the export got changed in the middle. If only for that reason, I don't think we could forbid a client from doing this. >> (Um, but that's pretty weird that the server's advertising an empty >> list. What's the nfs-utils version?) >> >> > > > [tdh@adept root]> yum list nfs-utils > Loaded plugins: dellsysidplugin2, fastestmirror, refresh-packagekit > updates/metalink > | 2.9 kB > 00:00 > updates > | 4.4 kB > 00:00 > Installed Packages > nfs-utils.i586 > 1:1.1.5-6.fc11 > installed Thanks! Hm. So this change of mine: 603017f2c1587d760e2649b889b581ca267ffee7 "Determine supported pseudoflavors from export" is probably at fault. I guess we need to figure out why it's producing a zero-length array. --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
