glusterfs.git/xlators/protocol, 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

fail revalidate properly

2009-10-09T15:42:38+00:00

fail revalidate calls if inoode number has changed for the basename at the server side. This is a temporary workaround for most of the cases till inode-gen is merged

Avati

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

Changed occurrences of Z Research to Gluster.

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

Signed-off-by: Anand V. Avati

protocol/client: access glusterfs context from the ctx member of xlator object

2009-09-22T13:13:43+00:00

- A global context pointer cannot be used with libglusterfsclient, since
    there can be many contexts in a single process.

Signed-off-by: Anand V. Avati 

BUG: 271 (applications using booster protocol/client crash in client_setvolume_cbk.)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=271

client-protocol: fix race-condition encountered while accessing fdctx

2009-09-22T13:13:35+00:00

- In protocol/client, fdctx is accessed by two sets of procedures,
  protocol_client_mark_fd_bad falls in one set whereas the other set consists of
  all fops which receive fd as an argument. The way these fdctxs are got is
  different in these two sets. While in the former set, fdctx is accessed
  through conf->saved_fds, which is a list of fdctxs of fds representing
  opened/created files. In the latter set, fdctxs are got directly from fd
  through fd_ctx_get(). Now there can be race conditions between two threads
  executing one procedure from these two sets. As an example let us consider
  following scenario:

  A flush operation is timed out and polling thread executing
  protocol_client_mark_fd_bad, fuse thread executing client_release. This can
  happen because, immediately a reply for flush is written to fuse, a release on
  the same fd can be sent to glusterfs and the polling thread still might be
  doing cleanup. Consider following set of events:

  1. fuse thread does fd_ctx_get (fd).
  2. polling thread gets the same fdctx but through conf->saved_fds.
  3. Now both threads go ahead and does list_del (fdctx) and eventually free
     fdctx.

  In other situations the same set events might occur and the threads
  executing fops other than flush in the second set might be accessing a
  fdctx freed in protocol_client_mark_fd_bad.

Signed-off-by: Anand V. Avati 

BUG: 127 (race-condition in accessing fdctx in protocol/client)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=127

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

protocol/client: 'connecting' event is properly notified.

2009-08-21T02:05:24+00:00

when there are no servers available to client, and transport init is
not successful, send 'connecting' event once to parent so it doesn't
hand in there.

Signed-off-by: Anand V. Avati 

BUG: 224 (Client hangs if none of the servers are up)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=224

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