kernel/include/linux/sunrpc/svc_xprt.h, branch linux-3.17.y

SUNRPC: Allow svc_reserve() to notify TCP socket that space has been freed

2014-07-29T20:10:20Z

Signed-off-by: Trond Myklebust Signed-off-by: J. Bruce Fields

svcrdma: Select NFSv4.1 backchannel transport based on forward channel

2014-07-18T15:35:45Z

The current code always selects XPRT_TRANSPORT_BC_TCP for the back channel, even when the forward channel was not TCP (eg, RDMA). When a 4.1 mount is attempted with RDMA, the server panics in the TCP BC code when trying to send CB_NULL. Instead, construct the transport protocol number from the forward channel transport or'd with XPRT_TRANSPORT_BC. Transports that do not support bi-directional RPC will not have registered a "BC" transport, causing create_backchannel_client() to fail immediately. Fixes: https://bugzilla.linux-nfs.org/show_bug.cgi?id=265 Signed-off-by: Chuck Lever Signed-off-by: J. Bruce Fields

SUNRPC: track whether a request is coming from a loop-back interface.

2014-05-22T19:59:18Z

If an incoming NFS request is coming from the local host, then nfsd will need to perform some special handling. So detect that possibility and make the source visible in rq_local. Signed-off-by: NeilBrown Signed-off-by: J. Bruce Fields

NFSD: Ignore client's source port on RDMA transports

2014-05-22T19:55:48Z

An NFS/RDMA client's source port is meaningless for RDMA transports. The transport layer typically sets the source port value on the connection to a random ephemeral port. Currently, NFS server administrators must specify the "insecure" export option to enable clients to access exports via RDMA. But this means NFS clients can access such an export via IP using an ephemeral port, which may not be desirable. This patch eliminates the need to specify the "insecure" export option to allow NFS/RDMA clients access to an export. BugLink: https://bugzilla.linux-nfs.org/show_bug.cgi?id=250 Signed-off-by: Chuck Lever Signed-off-by: J. Bruce Fields

svcrpc: make svc_xprt_received static

2012-08-21T21:42:01Z

Note this isn't used outside svc_xprt.c. May as well move it so we don't need a declaration while we're here. Also remove an outdated comment. Signed-off-by: J. Bruce Fields

svcrpc: don't bother checking bad svc_addr_len result

2012-08-21T21:40:10Z

None of the callers should see an unsupported address family (only one of them even bothers to check for that case), so just check for the buggy case in svc_addr_len and don't bother elsewhere. Acked-by: Chuck Lever Signed-off-by: J. Bruce Fields

svcrpc: share some setup of listening sockets

2012-08-21T21:07:48Z

There's some duplicate code here. Signed-off-by: J. Bruce Fields

SUNRPC: search for service transports in network namespace context

2012-02-01T00:28:19Z

Service transports are parametrized by network namespace. And thus lookup of transport instance have to take network namespace into account. Signed-off-by: Stanislav Kinsbursky Signed-off-by: Trond Myklebust Acked-by: J. Bruce Fields

SUNRPC: create svc_xprt in proper network namespace

2011-12-06T21:20:42Z

This patch makes svc_xprt inherit network namespace link from its socket. Signed-off-by: Stanislav Kinsbursky Signed-off-by: J. Bruce Fields

svcrpc: make svc_delete_xprt static

2011-12-06T21:18:51Z

Signed-off-by: J. Bruce Fields