glusterfs.git/xlators/protocol/server, branch v2.0.10rc3

protocol/server: Do gf_flock to flock conversion at the right place

2010-03-11T10:19:48+00:00

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

BUG: 708 (solaris : ping pong test hangs)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=708

protocol/server: use properly filled loc_t for performing revalidates

2010-01-23T10:04:30+00:00

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

BUG: 567 (crash in server_lookup_cbk)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=567

Changed occurrences of Z Research to Gluster.

2009-10-07T10:53:02+00:00

Signed-off-by: Anand V. Avati

protocol/server: server_stub_resume should check for failure of lookup when oldloc.parent is NULL.

2009-09-14T05:10:31+00:00

Signed-off-by: Anand V. Avati 

BUG: 215 (crash on ib-verbs in 2.0.6-rc4)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=215

in server_rename if we do_path_lookup on the newloc and parent directory is not found, the server crashes.

2009-08-20T00:57:57+00:00

Signed-off-by: Anand V. Avati

added log message when server fails to send the reply frame

2009-08-17T21:38:10+00:00

As of now, if a frame submit fails on server, there are no logs,
and clients will have missing frames (which leads to 'hangs').
Supporting situation like this very tricky without proper log
messages. As a step to make our log message lean and meaningful,
this log is important.

Signed-off-by: Anand V. Avati 

BUG: 190 (missing frames due to larger reply message size.. (ib-verbs))
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=190

server-lookup: added path info from header to log message

2009-08-05T00:27:33+00:00

in the previous commit, the path info was removed to prevent the
segfault, which instead could have been provided from request
header directly. More specific information is required for debugging,
and hence adding the path log.

Signed-off-by: Anand V. Avati 

BUG: 189 (segfault in server-lookup)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=189

logging related bug fix in server_lookup()

2009-08-04T23:47:48+00:00

When 'dict_unserialize' failed, the log message was trying to
print 'state->loc.path' and 'state->ino', which gets filled in
later stages in flow. Caused segmentation fault when there was
a failure.

Signed-off-by: Anand V. Avati 

BUG: 189 (segfault in server-lookup)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=189

server-protocol: fix in server-loc-fill()

2009-07-28T16:42:41+00:00

to continue with 'hashed' inode, even if inode_path() on the inode
fails. This will is needed for few lock operations, to unlock the
lock held on inode. (ie, it fixes 'rm -rf *' hang issue, seen from
multiple clients).

Signed-off-by: Anand V. Avati 

BUG: 112 (parallel deletion of files mounted by different clients on the same back-end hangs and/or does not completely delete)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=112

protocol/server: add checks for updatation of loc->parent in entrylk() or inodelk().

2009-07-27T18:33:56+00:00

entrylk() and inodelk() should try to update loc->parent only if parent is not-NULL.
because it is not an error to have loc->parent == NULL for entrylk() and inodelk()
operations.

Signed-off-by: Anand V. Avati 

BUG: 162 (Replication segfaults with many nodes)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=162