On Thursday July 17, SteveD@xxxxxxxxxx wrote: > > In kernels up to and including 2.6.26, mount reports "connection > > refused" type messages as EIO rather than EPROTONOSUPPORT. > > So detect those kernels and don't treat EIO as so fatal. > Should we just fix the kernel to do the right thing? Undoubtedly we should fix the kernel to do the right thing. But some people find it much easier to upgrade user-space tools like nfs-utils than to upgrade kernels. We already have code in mount.nfs to cope with earlier kernels which had less complete interfaces with userspace. We can see this lack of distinction in error code simple as a less complete interface in earlier kernels and treat it the same way. I don't feel so strongly about this that I will fight to the end, but I really think that if we can make life easier for our users with compromising our integrity, we should. And handling EIO differently depending on kernel version seems to fit that goal. NeilBrown -- 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
