glusterfs.git/xlators, branch v2.0.9

performance/stat-prefetch: fix memory leak.

2009-12-06T17:28:56+00:00

- rbt_hash_remove only removes entry from the hash table. It does not free
    the data.

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

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

fuse-bridge: fix memory leak during error handling.

2009-12-06T17:28:45+00:00

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

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

performance/stat-prefetch: don't check whether previous lookups have been failed in sp_process_inode_ctx.

2009-12-06T17:28:41+00:00

We need this patch for following reasons:
   1. The inode used in the successful lookup call may not be the one passed to
      fops operating on path. This may happen, if revalidate of inode is failed,
      but the lookup itself succeeds (in case of reavalidate failures, fuse
      sends a fresh lookup using new inode) and since inode_link, if there is an
      inode already associated with a path retains it.
   2. Only fops that "wait" in stat-prefetch on a lookup which is already in
      progress, need to check for the result of the lookup they are waiting on,
      before resuming and sp_process_inode_ctx is _not_ used in such contexts.

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

BUG: 428 (looks like stat cache not upto date..)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=428

performance/stat-prefetch: add "caller" arguement to sp_process_inode_ctx.

2009-12-06T17:28:38+00:00

- since sp_process_inode_ctx is called by many fops, if the context is not
    set "caller" argument can be logged in log msgs to identify caller.

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

BUG: 257 (Backport stat-prefetch to 2.0)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=257

performance/stat-prefetch: refactor sp_lookup_cbk to use sp_update_inode_ctx.

2009-12-06T17:28:34+00:00

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

BUG: 257 (Backport stat-prefetch to 2.0)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=257

performance/stat-prefetch: dont check for inode context in fops like create, mkdir.

2009-12-06T17:28:31+00:00

- context will not be set as a fresh inode is passed in each of these calls.
    instead create a new context.

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

BUG: 257 (Backport stat-prefetch to 2.0)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=257

performance/stat-prefetch: get inode context from local->loc.inode instead of inode passed as arguement in sp_lookup_cbk.

2009-12-02T19:00:07+00:00

- @inode in sp_lookup_cbk may be NULL in case of failure of lookup.

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

BUG: 426 (stat on mount point hangs.)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=426

Add support in rbthash to make use of user provided mempool.

2009-12-02T19:00:03+00:00

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

BUG: 221 (stat prefetch implementation)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=221

performance/stat-prefetch: make lookup to wait for the completion of another lookup on same path if one is in progress.

2009-12-02T19:00:00+00:00

- If current lookup (2) does not wait for completion of the lookup (1) which
    is in progress, there can be a race condition where (2) completes ahead of
    (1) and resuming all the waiting operations in the queue. When (1) returns,
    the original operation (eg., stat, chmod etc) might've already unwound and
    hence the frame would've been destroyed.

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

BUG: 257 (Backport stat-prefetch to 2.0)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=257

performance/stat-prefetch: fix errors in handling memory allocation failures in sp_inode_ctx_process.

2009-12-02T18:59:56+00:00

- the variables that are used for making decisions are assigned before
    memory allocations and these variables were not reset to
    correct values in case of memory allocation failures.

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

BUG: 257 (Backport stat-prefetch to 2.0)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=257