Hi Bruce-
Here's what I'm considering.
If the kernel detects that user space doesn't support rpcbind protocol
version 4, it falls back to version 2. If it is trying to register an
IPv6 RPC service, it fails outright.
All of this can be disabled completely in favor of legacy behavior by
disabling CONFIG_SUNRPC_REGISTER_V4.
In addition, I will add CONFIG options to enable/disable lockd and NFSD
listening on IPv6 sockets, to prevent all this noise for anyone using
classic IPv4-only. These will appear only if CONFIG_SUNRPC_REGISTER_V4
is enabled.
I haven't yet pursued why the kernel doesn't report the program version
mismatch to higher layers. That will be needed to make these changes
work correctly.
These patches have been compile-tested only.
---
Chuck Lever (3):
SUNRPC: Clearer error message when user space is running portmap
SUNRPC: Clearer error message when user space is running portmap
SUNRPC: Don't use EPROTONOSUPPORT in svc_register()
net/sunrpc/svc.c | 99 ++++++++++++++++++++++++++++++++++++++++++++++--------
1 files changed, 84 insertions(+), 15 deletions(-)
--
Chuck Lever <chuck.lever@xxxxxxxxxx>
--
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
