glusterfs.git/xlators/nfs/server/src/nfs-common.c, branch v3.4.0alpha2

nfs: do not change root inode if enable-ino32 is set

2012-11-18T17:43:04+00:00

When a user sets nfs.enable-ino32 on,
the root inode, which must be 1, is jumbled during
hashing of the gfid into 32 bits.
This patch avoids doing that, and returns inode of 1
for the root inode.

Change-Id: Ib65f2660998a95e1059be32bc298485c5cbe52df
BUG: 864222
Signed-off-by: Rajesh Amaravathi 
Reviewed-on: http://review.gluster.org/4154
Reviewed-by: Kaleb KEITHLEY 
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

nfs: resolve parent inode during inode_loc_fill

2012-11-13T07:59:59+00:00

This commit resolves the parent inode in nfs_inode_loc_fill
if the inode has a resolved path.

Change-Id: If407c91c246b0b9f3349cedae0baec8bd6831d10
BUG: 872923
Signed-off-by: Rajesh Amaravathi 
Reviewed-on: http://review.gluster.org/4157
Reviewed-by: Krishna Srinivas 
Tested-by: Gluster Build System

nfs: do lookup on getattr after brick-status change

2012-10-19T14:16:33+00:00

By doing a lookup, we get a chance to do all of the self-heal checks that
would occur if we were using native protocol, and return proper status if
the self-heal fails.  Best of all, we don't need to misrepresent times.

Change-Id: I76477d1e5fce4d83e4029e02fcdd71e81e23110d
BUG: 830134
Signed-off-by: Jeff Darcy 
Reviewed-on: http://review.gluster.org/4058
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

remove useless if-before-free (and free-like) functions

2012-07-13T21:03:42+00:00

See comments in http://bugzilla.redhat.com/839925 for
the code to perform this change.

Signed-off-by: Jim Meyering 
BUG: 839925
Change-Id: I10e4ecff16c3749fe17c2831c516737e08a3205a
Reviewed-on: http://review.gluster.com/3661
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

nfs-common: don't let 0-length path cause buf[-1] access

2012-07-12T02:13:09+00:00

Change-Id: I5f0e93448a954aff1ff08a0980fb9bfd60e63988
BUG: 789278
Signed-off-by: Jim Meyering 
Reviewed-on: http://review.gluster.com/3594
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

nfs: do not call inode_path on the newly created inode

2012-03-14T12:57:18+00:00

While resolving, for building the path into the loc, inode_find
is called with gfid as argument to get the inode from the inode
table. If the inode is not found, then a new inode is created.
Then the path is build using inode_path. But if the inode is
not linked to inode table (newly created inode), then gfid will
be null and inode_path returns null gfid as the path. Suppose the
lookup operation on that gfid fails, then we print the null gfid
in the log message.

To avoid it, build the path using the gfid only if inode_path
fails.

Change-Id: I2506fa8675761ddb0bc02980cd3583d9d068fc85
BUG: 802424
Signed-off-by: Raghavendra Bhat 
Reviewed-on: http://review.gluster.com/2930
Tested-by: Gluster Build System 
Reviewed-by: Amar Tumballi 
Reviewed-by: Vijay Bellur

nfs: changes for using nameless lookup and anonymous FDs

2012-01-20T13:06:15+00:00

- Use gfid to create filehandle instead of encoding path components
- Utilize nameless lookups of GFID for deep resolution instead of
  crawling the namespace with component hints
- Use anonymous FDs for file based operations
- Do away with fdcaching code for files and dirs

Change-Id: Ic48fb23370b25d183f7e1fc1cc5dffa9d5bab3fb
BUG: 781318
Reviewed-on: http://review.gluster.com/2645
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

core: remove 'ino' variable from 'inode_t' structure

2011-11-16T11:44:32+00:00

Change-Id: I0f078d1753db65d2f2e0380d1b0450c114cf40dd
BUG: 3518
Reviewed-on: http://review.gluster.com/522
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

NFS: logging enhancement.

2011-11-16T10:05:27+00:00

Change-Id: Ie1731a6b2b63e07bc49a84c2f9dd87c5b50a9f53
BUG: 3527
Reviewed-on: http://review.gluster.com/573
Tested-by: Gluster Build System 
Reviewed-by: Amar Tumballi 
Reviewed-by: Vijay Bellur

Fix memleaks in NFS

2011-11-15T10:39:27+00:00

Change-Id: I522d4bad71d1e914fa88367f70f5e8c28d64fbbe
BUG: 3542
Reviewed-on: http://review.gluster.com/533
Tested-by: Gluster Build System 
Reviewed-by: Amar Tumballi 
Reviewed-by: Shehjar Tikoo