glusterfs.git/xlators/protocol/server/src/server3_1-fops.c, branch v6.0rc1

xlators/protocol: better filename

2012-07-04T18:56:59+00:00

3_1 name was used for very first version of GlusterFS which
used RPC for its protocol, even though we changed protocol
after 3.1.x, we kept the name of few files as is. Changed
the file names to something better.

Change-Id: I297f1979e7c7e909e60674eec2e632506bc776f5
BUG: 764890
Signed-off-by: Amar Tumballi 
Reviewed-on: http://review.gluster.com/3628
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

protocol/server: do not wind opendir call if fd creation fails

2012-06-01T20:09:08+00:00

If resolve fails in some fd based operation, then do not use fd to get
gfid (fd might be NULL). Use the gfid present in resolve structure.

Change-Id: I1058274a2f9b4e58a76e4e6019e7c5ce1906d365
BUG: 827376
Signed-off-by: Raghavendra Bhat 
Reviewed-on: http://review.gluster.com/3504
Tested-by: Gluster Build System 
Reviewed-by: Brian Foster 
Reviewed-by: Jeff Darcy 
Reviewed-by: Anand Avati

protocol: do not log getxattr/ENODATA as warning

2012-05-30T05:57:18+00:00

When SELinux is enabled, most of the files do not have labels and
result is a ton of unnecessary logs

Change-Id: I0e781e2fb6bcfb3fb12298175a41f7b981af9c39
BUG: 811217
Signed-off-by: Anand Avati 
Reviewed-on: http://review.gluster.com/3486
Tested-by: Gluster Build System 
Reviewed-by: Amar Tumballi

server protocol : logging and negative case logic fixes

2012-05-30T04:34:01+00:00

* log 'resolve' gfid, instead of inode gfid, which fails to log
  for everything which fails to resolve.

* in case of 'op_ret == -1' never look into xdata or any other
  argument.

* bring uniformity in the _cbk() code.

BUG: 821139

This patch is not complete fix for above mentioned bug, but is
useful the debug it properly

Change-Id: I159becdde70720cba072e494f70951395dc6868f
Signed-off-by: Amar Tumballi 
Reviewed-on: http://review.gluster.com/3437
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

rpc: fix the vecsizer issue

2012-05-25T00:32:32+00:00

* currently, we needed 'base-address' of the header for glusterfs
  writev vecsizer and 'current-address' of the buffer which is
  reading the data on socket, for nfs write vecsizer.

* nfs write issues started coming after http://review.gluster.com/3182
  was pushed into repo, now fixed.

* fixed by sending both as argument for vecsizer from the transport

Change-Id: I6db360ce265ce5f083f1794ebdb3867f8cfad9ec
Signed-off-by: Amar Tumballi 
BUG: 824472
Reviewed-on: http://review.gluster.com/3431
Tested-by: Gluster Build System 
Reviewed-by: Jeff Darcy 
Reviewed-by: Anand Avati

protocol: handle proper vector size for writev()/readv()

2012-05-21T23:50:57+00:00

* fixes the offset handling issue when 'xdata' is sent in writev/readv fop
  at the transport layer itself.
* client_writev() was not sending xdata on wire, fixed

Change-Id: Ib5ced64c84d415f07032662017979c65d9a1a128
Signed-off-by: Amar Tumballi 
BUG: 808078
Reviewed-on: http://review.gluster.com/3182
Tested-by: Gluster Build System 
Reviewed-by: Jeff Darcy 
Tested-by: Jeff Darcy 
Reviewed-by: Anand Avati

protocol/server: fix a crash with NULL dereference

2012-05-21T04:21:20+00:00

in setxattr() and fsetxattr() _cbk functions

Change-Id: I9798d182e7f68509e8e37d43cb18e4c2f4bd6fab
Signed-off-by: Amar Tumballi 
BUG: 823244
Reviewed-on: http://review.gluster.com/3384
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

protocol/{client,server} : Log improvements

2012-05-08T11:06:38+00:00

Make use of gfid in log messages.

Change-Id: I28548be64d19418f99ee9ccdbd3ac4ae67c6c015
BUG: 814666
Signed-off-by: Kaushal M 
Reviewed-on: http://review.gluster.com/3274
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

libglusterfs/inode.c: do not link the inode in the dentry cache for "." and ".."

2012-05-05T19:42:31+00:00

Change-Id: I18c2e090c1ca64f47ce70dc63c9f73ea7def2f86
BUG: 810828
Signed-off-by: Krishna Srinivas 
Reviewed-on: http://review.gluster.com/3220
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

protocol: fix memory leak of lk-owner buffer in *lk() calls

2012-05-03T20:03:51+00:00

Change-Id: I7fb0e1757c5e04b1a2609c9822ac79301808f671
Signed-off-by: Amar Tumballi 
BUG: 768330
Reviewed-on: http://review.gluster.com/3244
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati