Hi Bruce, Trond-
I've tossed out the previous strategy for managing RPC registration
upcalls. The kernel now adjusts automatically to whatever the local
portmap daemon supports.
If IPv6 is enabled in the kernel, RPC services will get an AF_INET6
listener, but if the system has a portmapper capable only of rpcbind
v2, only IPv4 services are registered.
We can get rid of CONFIG_SUNRPC_REGISTER_V4 entirely.
I've tested this approach on FC6 (legacy portmap) and F9 (new rpcbind)
as both client and server.
Thoughts?
---
Chuck Lever (6):
SUNRPC: Remove CONFIG_SUNRPC_REGISTER_V4
SUNRPC: rpcb_register() should handle errors silently
SUNRPC: Simplify kernel RPC service registration
SUNRPC: Simplify svc_unregister()
SUNRPC: Don't return EPROTONOSUPPORT in svc_register()'s helpers
SUNRPC: Use IPv4 loopback for registering AF_INET6 kernel RPC services
fs/Kconfig | 22 ----------
fs/lockd/svc.c | 7 +--
net/sunrpc/rpcb_clnt.c | 25 +++---------
net/sunrpc/svc.c | 102 +++++++++++++++++++++---------------------------
4 files changed, 55 insertions(+), 101 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
