On Jul 6, 2009, at 1:58 PM, Trond Myklebust wrote:
On Mon, 2009-07-06 at 13:51 -0400, Chuck Lever wrote:
In both cases, it turns out that the library implementations in user
space already fail quickly. RPC_CANTRECV is returned if an attempt
is
made to send an rpcbind query to an inactive UDP port.
RPC_SYSTEMERROR/ECONNREFUSED is returned if an attempt is made to
send
an rpcbind query to an inactive TCP port. In my view, the kernel is
lacking here, and should be made to emulate user space more closely.
I fully agree that we can fix the above by more judicious
interpretation
of the returned networking errors. What I don't see eye to eye with is
the assertion that has been floating about that the current behaviour
should be a good enough reason to add kernel AF_LOCAL support.
Since portmapper doesn't support it, and the kernel (for now) needs
backwards compatibility with portmapper, AF_LOCAL for rpcbind is
rather a non-starter.
In my opinion there are other reasons to consider kernel-level
AF_LOCAL support at some later point.
--
Chuck Lever
chuck[dot]lever[at]oracle[dot]com
--
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
