glusterfs.git/xlators/protocol/server/src, branch v3.0.2

Revert "Server backend storage hang should not cause the mount point to hang."

2010-01-26T15:23:19+00:00

This reverts commit a0b148ea4e2a0163548eeb89b7580be4adbb8070.

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

BUG: 272 (Server backend storage hang should not cause the mount point to hang)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=272

protocol/server: unlink dentry only for non-root inodes

2010-01-26T11:47:23+00:00

in server_lookup_cbk, unlink dentry from the crash on receiving
ENOENT from subvolume only for non-root inode. ENOENT can be returned
for root inode if export directory is deleted

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

BUG: 526 (glusterfsd crash when export dir is deleted and revalidate happens on /)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=526

protocol/server: cleanup whitespaces

2010-01-23T10:58:38+00:00

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

BUG: 272 (Server backend storage hang should not cause the mount point to hang)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=272

Server backend storage hang should not cause the mount point to hang.

2010-01-23T10:58:34+00:00

Submitted-by: Krishna Srinivas 
NOTE: fixed compilation issues in posix.c introduced while merging

storage/posix polls for FS/kernel being functional by issuing
statvfs() call. In case statvfs expires the timer, storage/posix will
send CHILD_DOWN to upper translator. Ultimately this will cause
protocol/server to disconnect all clients connected and also cleans up
the data structures. Hence if soft lockup or other kernel bug causes
backend FS to hang, the clients will not be hung.

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

BUG: 272 (Server backend storage hang should not cause the mount point to hang)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=272

protocol/server: handle group id decoding in a stricter way

2010-01-23T07:01:48+00:00

This causes crash between 3.0.x servers and 2.0.x clients

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

BUG: 564 (3.0.1rc3 server daemon crashes when any of the 2.0.x version client connects)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=564

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

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