glusterfs.git/xlators/nfs/server/src, branch v3.2.5qa3

gnfs/server: allow 255-char file names

2011-10-01T12:55:41+00:00

* Posix requires 255 character filenames(NAME_MAX), so
buffer to store a filename should be 256(+1 for
terminating '\0' character).

Change-Id: Id06ffa0e2d90a5950198cda3e4146ff10d25308b
BUG: 3572
Reviewed-on: http://review.gluster.com/500
Tested-by: Gluster Build System 
Reviewed-by: Amar Tumballi 
Reviewed-by: Krishna Srinivas

NFS : Posix compliance fixes.

2011-09-22T05:37:17+00:00

Change-Id: I3687fd16bcc0ddc8a352efb9a0b410f54bec6e74
BUG: 1337
Reviewed-on: http://review.gluster.com/482
Tested-by: Gluster Build System 
Reviewed-by: Amar Tumballi 
Reviewed-by: Vijay Bellur

mount/nfs: Gluster nfs crashes with subdirectory mount

2011-09-08T06:55:18+00:00

Glusterfs used to crash trying to dereference a NULL
pointer. Also, in mnt3_resolve_export_subdir, volume
name was prefixed to sub directory exported, resulting in
mount fail of sub directory. Fixed both issues.

Change-Id: I746f0c244b4cbf03033d73ac3e40518762d76385
BUG: 3481
Reviewed-on: http://review.gluster.com/346
Tested-by: Gluster Build System 
Reviewed-by: Shehjar Tikoo

nfs3: Resolve entry vs. hash conflict at same dir depth

2011-09-08T06:53:55+00:00

Intro Note
==========
The current code in hard fh resolution takes the first-match approach, i.e.
which ever dirent either matches the hash or matches the gfid first
is the one chosen as the result for the next step of fh resolution. In
the latter case, i.e., dirent matches the gfid, we the next step is to
conclude the fh resolution by returning the entry whose gfid matched.
In the former, i.e., the hash matches the dirent, we choose the hash-matching
dirent as the next directory to descend into, for searching the file to be
operated upon.

Problem
=======
When performing hard fh resolution, there can be a situation where:

o the hash of the primary entry,i.e. the entry we're looking for and the hash
of another sibling directory, match. Note the use of "sibling", meaning both
the primary entry and the hash matching one are in the same directory, i.e.,
their filehandle.hashcount will be same.

o the sibling directory is encountered first during the dir search.

Because of the current code described in "Intro", we'll end up descending into
the sibling directory even though the correct behaviour is to ignore this and
wait till we encounter the primary entry in the same parent directory.

Once we end up descending into this sibling directory, the directory depth
validation check fails. The check fails because it notices that the resolution
is attempting to open a directory that is deeper in the fs tree than the file
we're looking for. When this check fails, we return an ESTALE. So basically, a
false-positive results in an estale to Specsfs.

This is not a theoretical situation. Me and Avati saw this on specsfs test
where sfs created terabytes-sized file system for its tests. The number of
files was so huge in a single directory that the hashes of two entries ended up
colliding.

Change-Id: I78d8756252330201e165d788a29277b4bce0df90
BUG: 3510
Reviewed-on: http://review.gluster.com/358
Tested-by: Gluster Build System 
Reviewed-by: Shehjar Tikoo

xlators/nfs: Fix a typo in option description

2011-08-20T10:35:23+00:00

Change-Id: Ibb888357b87603544f360d181637138261fb3b71
BUG: 3445
Reviewed-on: http://review.gluster.com/275
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

mgmt/Glusterd: Implementation volume set help/help-xml

2011-08-19T05:42:48+00:00

Change-Id: I0c54fd1c15550e5e5551e95ed32adb14d8029fab
Reviewed-on: http://review.gluster.com/238
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

Change Copyright current year

2011-08-10T17:57:44+00:00

Change-Id: Id1f1a91cf15d933d5621a0073ddaebe02df0f159
BUG: 3348
Reviewed-on: http://review.gluster.com/198
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

LICENSE: s/GNU Affero General Public/GNU General Public/

2011-08-06T13:40:14+00:00

Change-Id: Ibf5f45431d7a55b70d7304649af652d6f25bb688
BUG: 3348
Reviewed-on: http://review.gluster.com/183
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

NFS access control list: Decode the NFS requests into mode format

2011-07-07T12:45:13+00:00

Signed-off-by: shishir gowda 
Signed-off-by: Vijay Bellur 

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

nfs: Change NFS3 access op to use access fop

2011-07-05T12:21:20+00:00

This change is needed so that we have a uniform dependence on
posix-acl for permission checks as well as ACL checks.

Signed-off-by: Shehjar Tikoo 
Signed-off-by: Vijay Bellur 

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