glusterfs.git/xlators/protocol/server/src/server-helpers.c, branch v3.2.5qa9

Change Copyright current year

2011-08-10T17:57:44+00:00

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

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

2011-08-06T13:40:14+00:00

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

server: Reassociating 'old' conn can lead to chaos.

2011-07-12T12:38:10+00:00

Since we moved to a single socket connection b/w client and server,
inherting connection state is unnecessary and can sometimes be
dangerous when clients reconnect even before the server detects
a socket error on the old connection.

Dirty detail: This reassociation results in 'ref count' not decreasing
in tandem with the connection disconnects. This results in a resource
leak.

Signed-off-by: Krishnan Parthasarathi 
Signed-off-by: Anand Avati 

BUG: 3104 (Self-heal does not work in dis-rep!)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3104

removed reference to GF_LOG_NORMAL

2011-04-07T18:40:25+00:00

instead used GF_LOG_INFO, which is more standard log level.

Signed-off-by: Amar Tumballi 
Signed-off-by: Vijay Bellur 

BUG: 2669 (RuntimeError: cannot recognize log level "normal")
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2669

do not check loc and fd since they can be passed as NULL only

2011-03-23T07:13:56+00:00

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

BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

protocol/server: log enhancements

2011-03-17T18:59:12+00:00

Signed-off-by: Amar Tumballi 
Signed-off-by: Vijay Bellur 

BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

protocol/server: White space cleanup and NULL check validations.

2011-03-17T18:59:08+00:00

Signed-off-by: Junaid 
Signed-off-by: Amar Tumballi 
Signed-off-by: Vijay Bellur 

BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

Logging : Use of uuid_utoa and uuid_utoa_r.

2011-02-04T08:39:26+00:00

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

BUG: 2308 (Threadsafe uuid to string conversion function)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2308

protocol/server: Distinguishing the locks based on the type of fop like inodelk and entrylk.

2011-01-24T22:19:44+00:00

Currently, the protocol server considers entrylk to be held only on directories
and inodelk on files and thus when a client unmounts itself while holding locks,
it fails to free entrylk locks held on files and inodelk locks held on directories.

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

BUG: 2221 (Failed to free Inodlk locks on directories when the client holding the locks was unmounted before releasing the locks held.)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2221

protocol/rpc/transport: bring in one more event for 'TRANSPORT-DESTROY'

2010-10-07T12:09:08+00:00

needed because, a RPC disconnect doesn't mean that a RPC transport/listener
is dead. With this, the race in server protocol cleaning up the lock table /
fd table when some frames are in transit will be handled properly.

Signed-off-by: Amar Tumballi 
Signed-off-by: Vijay Bellur 

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