glusterfs-snapshot.git/api/src, branch work

core: block unused signals in created threads

2013-09-25T08:33:16+00:00

Block all signal except those which are set for explicit handling
in glusterfs_signals_setup(). Since thread spawning code in
libglusterfs and xlators can get called from application threads
when used through libgfapi, it is necessary to do this blocking.

Change-Id: Ia320f80521a83d2edcda50b9ad414583a0175281
BUG: 1011662
Signed-off-by: Anand Avati 
Reviewed-on: http://review.gluster.org/5995
Tested-by: Gluster Build System 
Reviewed-by: Amar Tumballi 
Reviewed-by: Vijay Bellur

logging: Expose set_log_file_path() in libglusterfs.

2013-09-24T19:00:54+00:00

This patch also changes the behavior of glfs_set_logging().
If logfile argument is not provided to glfs_set_logging(),
libgfapi uses set_log_file_path() to create a logfile.

Change-Id: I49ec66c7f16f5604ff2f7cf7b365b08a05b5460d
BUG: 764890
Signed-off-by: Vijay Bellur 
Reviewed-on: http://review.gluster.org/5910
Reviewed-by: Anand Avati 
Tested-by: Anand Avati

gfapi: implement a minimial glfs_fini()

2013-09-17T18:42:12+00:00

At the very least, we should PARENT_DOWN on the currently active
graph and disconnect ourselves from glusterd.

Further cleanups underway.

Change-Id: I9276686a84b0975b5ce272b4cbec1b80920d5c5c
BUG: 1004519
Signed-off-by: Anand Avati 
Reviewed-on: http://review.gluster.org/5788
Tested-by: Gluster Build System 
Reviewed-by: Raghavendra Bhat 
Reviewed-by: Amar Tumballi

gfapi: use native STACK_WIND for read _async() calls

2013-09-17T18:41:42+00:00

There is little value in using synctask wrappers for async IO
requests, as STACK_WIND is asynchronous by nature already.

Skip going through synctask for read/write async calls.

Change-Id: Ifde331d7c97e0f33426da6ef4377c5ba70dddc06
BUG: 1009134
Signed-off-by: Anand Avati 
Reviewed-on: http://review.gluster.org/5897

gfapi: store the open/create flags in fd_t object

2013-09-06T22:56:57+00:00

The flags passed on to open and create calls were not being saved
in the fd_t object, hence the fd migration was failing.

Change-Id: I486bb818477fe4c393d64a711534a082162a0e53
BUG: 1005159
Signed-off-by: Poornima 
Reviewed-on: http://review.gluster.org/5837
Reviewed-by: Amar Tumballi 
Reviewed-by: Raghavendra Bhat 
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

gfapi: apply an upper bound on nested symlink resolution

2013-09-05T12:26:30+00:00

In case of nested symlink resolution, implement an upper
bound on the number of such nested levels the resolver will
descend. This limit is arbitrary, and set to 2048 nested
levels.

Change-Id: I264e5bd60d317eda97f4e6f49bd5d8694f8664a9
BUG: 1004100
Signed-off-by: Anand Avati 
Reviewed-on: http://review.gluster.org/5768
Tested-by: Gluster Build System 
Reviewed-by: Raghavendra Talur 
Reviewed-by: Vijay Bellur

glusterfs, gfapi: fix symbol clash

2013-09-05T12:24:42+00:00

The callback structures in both protocol/client and glusterfsd,
gfapi used the same name for the actor table - gluster_cbk_actors.

CBKs are required only for the management connection, and the
actors of protocol/client are NOP functions. This supposed-to-be
NOP function dispatch tabble is actually ending up pointing to
the actor table of glusterfsd or gfapi.

These functions, even though set wrongly, are not even expected
to be called through the protocol/client callback path. Glusterd
however sends the FETCHSPEC (and other) notify callbacks to *all*
connected clients unconditionally, and there is a small period
of time when protocol/client is connected to glusterd for
PORTMAP query. If the FETCHSPEC callback notify is issued in
this window of time, we end up calling the wrong actor in the
client side resulting in a crash.

Change-Id: I605ff7df64c7faf4607369bbf275aedec28e1778
BUG: 1004091
Signed-off-by: Anand Avati 
Reviewed-on: http://review.gluster.org/5767
Tested-by: Gluster Build System 
Reviewed-by: Amar Tumballi

api: Add null check for active_subvol in glfs_close.

2013-08-29T21:11:50+00:00

Problem:
In glfs_close, NULL value returned by glfs_active_subvol was not
being checked and was causing a crash.

Change-Id: I6eefa60e7b07dee251b98932b1d08a5c2981d3d7
BUG: 1002511
Signed-off-by: Raghavendra Talur 
Reviewed-on: http://review.gluster.org/5733
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

api: Fill loc.path and loc.gfid before syncop_open.

2013-08-29T20:52:28+00:00

syncop_open was crashing because of NULL dereference.
This fixes that.

Change-Id: I4bc48fac2a6c0b15c806cbbb4ae45c67891ab7ed
BUG: 1002577
Signed-off-by: Raghavendra Talur 
Reviewed-on: http://review.gluster.org/5734
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

synctask: minor enhancements

2013-08-28T22:52:24+00:00

- Enhance syncenv_new() to accept scaling parameters of syncproc.
  Previously the scaling parameters were hardcoded and decided at
  compile time.

- New API synctask_create() which returns the created synctask. This
  is similar to synctask_new which only returned the status of whether
  a synctask could be created or not.

  The meaning of NULL cbk in synctask_create() means the task is
  "joinable". Until synctask_join() is called on such a synctask,
  the task is not reaped and resources are not destroyed. The
  task would be in a zombie state after synctask_fn returns and
  before synctask_join() is called.

Change-Id: I368ec9037de9510d2ba951f0aad86aaf18d9a6b6
BUG: 986775
Signed-off-by: Anand Avati 
Reviewed-on: http://review.gluster.org/5365
Tested-by: Gluster Build System 
Reviewed-by: Brian Foster