glusterfs.git/rpc, branch v3.1.6qa8

LICENSE: s/GNU Affero General Public/GNU General Public/

2011-08-06T13:36:02+00:00

Change-Id: I30b1807f4493a9b4ffa9899548daf7d29a0a6364
BUG: 3348
Reviewed-on: http://review.gluster.com/184
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

rpc: in client connection init(), return the proper error code

2011-07-28T11:14:45+00:00

without the proper error code, rpc won't know if transport is successfully
loaded or not.

Change-Id: Idc3ad56d2f47cf1e81ba39f90a7f7b47305d7d9a
BUG: 3260
Reviewed-on: http://review.gluster.com/114
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

rpc-transport/rdma: call ibv_fork_init to make rdma work with fork.

2011-07-01T08:26:42+00:00

Signed-off-by: Raghavendra G 
Signed-off-by: Anand Avati 

BUG: 3091 (rebalance fails with "transport endpoint not connected" in 3.2.1 rdma set-up)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3091

rpc-transport/rdma: don't return '0' in case of un-initiated rdma_connect()

2011-06-19T09:16:23+00:00

needed to handle the re-configuration of the port in client protocol. If
there is a successful 'connect()' after the query port, the remote-port
value gets reset to '0'. In this case, if the connect() return 0 for
already connected socket, the query_portmap will keep happening in a loop.

Signed-off-by: Amar Tumballi 
Signed-off-by: Anand Avati 

BUG: 2258 (enhance gluster volume rebalance)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2258

RPC : Valid typecasting for ipv4 and ipv6 in rpcsvc_get_listener_port.

2011-05-31T16:12:09+00:00

Signed-off-by: Gaurav 
Signed-off-by: Anand Avati 

BUG: 2956 (Invalid typecating for ipv4 and ipv6 in rpcsvc_get_listener_port.)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2956

Introduce client-allow-insecure xlator-option.

2011-05-31T16:12:04+00:00

Allows glusterfs clients to bind to any port and does not restrict it
to 1024.

This is a xlator-option only, and is not supported in volume set cmd.
The reason is, few clients may choose this, and few may not. Hence
only supported as a xlator-option during mount time.

For this to work with glusterfs, server.allow-insecure should be set
to on

Signed-off-by: shishir gowda 
Signed-off-by: Anand Avati 

BUG: 2868 (Add xlator-option to support insecure-bind for clients)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2868

rpc: Introduce option for listen()'s backlog

2011-05-31T16:11:50+00:00

Signed-off-by: Vijay Bellur 
Signed-off-by: Anand Avati 

BUG: 2941 (glusterd breaks when starting ~100 volumes)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2941

rpc: Don't warn on failure to bind to privileged port

2011-03-29T12:32:40+00:00

Signed-off-by: Pranith Kumar K 
Signed-off-by: Vijay Bellur 

BUG: 2582 (allow option to accept messages from insecure ports)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2582

rpc: Provide an option to allow insecure ports

2011-03-29T12:32:36+00:00

Signed-off-by: Pranith Kumar K 
Signed-off-by: Vijay Bellur 

BUG: 2582 (allow option to accept messages from insecure ports)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2582

rpc-transport/rdma: handle cases where peer is NULL in send_completion.

2011-03-12T13:10:39+00:00

- There can be valid cases where peer is NULL - For eg., race b/w pollin
    received on handshake socket and as a result transport getting disconnected
    and handling of a send/recv completion on the same qp for some previous
    read/write - in send/recv_completion_process. Hence we should be checking
    for a valid peer pointer before accessing it.

Signed-off-by: Raghavendra G 
Signed-off-by: Vijay Bellur 

BUG: 2514 ()
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2514