glusterfs.git/xlators/protocol, branch v3.0.0

resolver: include RESOLVE_EXACT type for failure case when inode not found

2009-12-07T13:31:40+00:00

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

BUG: 315 (generation number support)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=315

resolver: handle resolutions of paths

2009-12-06T19:44:48+00:00

support a new type of resolution where only the path is sent from the
client over the wire without inode/parent/generation numbers. this can
happen when cluster translators could not look up inodes on a server
and later when the server comes up applications issues operations on
the inode without a lookup (since they could be cd'ed inside). In these
cases the server makes the best attempt to resolve the path and perform
the fop on it

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

BUG: 315 (generation number support)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=315

Revert "protocol/client: return ENOENT if inode context is missing"

2009-12-06T19:34:07+00:00

This reverts commit 4439876a34f2e5d19db0d8b05ce7d7722c1c466f.

This revert is necessary for path handle resolution to work over the
protocol where client/server talk only with the path, without inode
or parent inode and generation numbers

protocol/server: more fixes in server_link_cbk

2009-12-06T16:41:37+00:00

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

BUG: 448 (server_link_cbk refers to @inode when op_ret is -1)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=448

protocol/server: fix bad reference to @inode in server_link_cbk

2009-12-06T10:30:17+00:00

when op_ret is -1, gf_log refers to @inode which can be NULL. fix
this to refer to state->loc2.inode instead

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

BUG: 448 (server_link_cbk refers to @inode when op_ret is -1)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=448

fix crash in server protocol server-connection-destroy

2009-12-05T08:49:22+00:00

a variable allocated inside a condition was getting reffered outside
the block. If the condition fails, there used to be a crash.

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

BUG: 439 (crash in server protocol, while destroying connection)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=439

protocol/client: return ENOENT if inode context is missing

2009-12-04T13:57:41+00:00

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

BUG: 315 (generation number support)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=315

protcol/server: server_connection_destroy - destroy frame after issuing flush

2009-12-04T09:46:23+00:00

frame was getting destroyed after unlocking, but before issuing flush. This
could result in corruption if an fd was opened between server_connection_cleanup
and server_connection_destroy because of pending open calls in io-threads at the
time of POLLERR disconnection

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

BUG: 430 (Server crash when client is killed)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=430

fixing some warnings on 64bit machine.

2009-12-03T21:54:57+00:00

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

BUG: 408 (warning while building on 64bit machine..)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=408

features/locks: Release all locks of an fd when a client disconnects.

2009-12-03T20:45:14+00:00

Signed-off-by: Pavan Vilas Sondur 
Signed-off-by: Anand V. Avati 

BUG: 336 (Use lock owner field from fuse in locks)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=336