glusterfs.git/rpc/rpc-lib, branch release-3.1

rpc: Need to keep ref when handling cbk in call_bail.

2011-09-20T09:06:03+00:00

Change-Id: Ic944599cfa2696a0ae77105185d49fb510ce6fec
BUG: 3511
Reviewed-on: http://review.gluster.com/397
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

Change Copyright current year

2011-08-10T17:58:03+00:00

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

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 : 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: 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 : Sending error reply on decodong failure.

2011-03-01T10:06:00+00:00

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

BUG: 2435 (Not able to send error reply in rpcsvc.)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2435

glusterd: separate out cli specific programs and mgmt specific programs

2011-03-01T10:05:51+00:00

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

BUG: 2333 (make glusterd more rpc friendly)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2333

rpcsvc: Handle more than one payload vectors.

2011-03-01T07:40:36+00:00

- fops like write can recieve payload data in more than one vector. This can
    happen with write-behind being loaded on client side.

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

BUG: 2454 (rdma data corruption)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2454