glusterfs.git/xlators/nfs/server/src, branch v3.3.0qa39

nlm: use correct subvolume when opening the file

2012-04-27T05:25:43+00:00

Change-Id: Ia0a482c89f10481184dc8f0f5b27cf6612ac114a
BUG: 816476
Signed-off-by: Krishna Srinivas 
Reviewed-on: http://review.gluster.com/3233
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

nfs/nlm: remove /var/run/rpc.statd.pid before starting rpc.statd.

2012-04-23T07:20:05+00:00

Sometimes rpc.statd fails to start if rpc.statd.pid exists.

Change-Id: Ic6feb375330fceb8dd6c35330757738fb5cbe16f
BUG: 814265
Signed-off-by: Krishna Srinivas 
Reviewed-on: http://review.gluster.com/3206
Tested-by: Gluster Build System 
Tested-by: Saurabh Jain 
Reviewed-by: Vijay Bellur

nlm: register client name with statd for blocking, nonblocking and reclaim lock calls

2012-04-20T13:01:50+00:00

Change-Id: If983f7b2f94703442e0745c5cbd2701edb2a972a
BUG: 809362
Signed-off-by: Krishna Srinivas 
Reviewed-on: http://review.gluster.com/3097
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

nfs/nlm: disable NLM if rpc.statd is not found.

2012-04-19T06:41:35+00:00

Change-Id: I571e1f14cefdfabecd8996b6d0ffc928464d2b51
BUG: 813258
Signed-off-by: Krishna Srinivas 
Reviewed-on: http://review.gluster.com/3174
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

nlm: send sm-notify to clients whenever the nfs server is restarted so that clients reclaim the locks.

2012-04-17T15:26:06+00:00

Change-Id: I0a8e291ad0a78e2e68070b1d289d32a786da8da2
BUG: 802885
Signed-off-by: Krishna Srinivas 
Reviewed-on: http://review.gluster.com/3096
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

nfs: option to disable NLM

2012-04-17T13:29:49+00:00

Adding support to disable/enable nlm with the following command:
         # gluster volume set  nfs.nlm [on|off]

Change-Id: I1ad3e44c5d4349d0f3463bfca0995fd10def39dd
BUG: 812869
Signed-off-by: Rajesh Amaravathi 
Reviewed-on: http://review.gluster.com/3160
Tested-by: Gluster Build System 
Reviewed-by: Krishna Srinivas

nfs/server: hard resolve fh on restart

2012-04-16T18:19:01+00:00

the filehandle passed to hard resolving code was not initialized
to it correct value (resovlefh).

Change-Id: I0a26c7b90bf3efec7fda26fed0823755c4b9e87b
BUG: 802779
Signed-off-by: Rajesh Amaravathi 
Reviewed-on: http://review.gluster.com/3150
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

xlator/server,xlator/nfs : Fix authentication for address lists

2012-04-13T07:55:51+00:00

Fixes authentication problems when address lists are given for
auth.{allow,reject} and nfs.rpc-auth-{allow,reject}.

Change-Id: I9959ebfa6820aef52c883372e1085660560e1e73
BUG: 810179
Signed-off-by: Kaushal M 
Reviewed-on: http://review.gluster.com/3104
Tested-by: Gluster Build System 
Reviewed-by: Amar Tumballi 
Reviewed-by: Vijay Bellur

nfs/nlm: dummy actor for FREE_ALL procedure

2012-04-05T12:10:40+00:00

NLM4_FREE_ALL rpc procedure has been provided nlm's
null procedure as actor to facilitate windows Nfs mounts.

NOTE: windows Nfs needs several other NLM procedures to work.
As a result, this patch only makes it possible to do a working
mount of a volume with "nolock" option in windows.
*Windows mount WITHOUT "nolock" option does NOT work as expected*

Change-Id: Ie163982497871312c5bb15f8c141fef460cadc34
BUG: 800287
Signed-off-by: Rajesh Amaravathi 
Reviewed-on: http://review.gluster.com/3063
Tested-by: Gluster Build System 
Reviewed-by: Krishna Srinivas

Replace GPLV3 MD5 with OpenSSL MD5

2012-04-04T23:13:21+00:00

Ric asked me to look at replacing the GPL licensed MD5 code with
something better, i.e. perhaps faster, and with a less restrictive
license, etc. So I took a couple hour holiday from working on
wrapping up the client_t and did this.

OpenSSL (nee SSLeay) is released under the OpenSSL license, a BSD/MIT
style license. OpenSSL (libcrypto.so) is used on Linux, OS X and *BSD,
Open Solaris, etc. IOW it's universally available on the platforms we
care about. It's written by Eric Young (eay), now at EMC/RSA, and I
can say from experience that the OpenSSL implementation of MD5 (at least)
is every bit as fast as RSA's proprietary implementation (primarily
because the implementations are very, very similar.) The last time I
surveyed MD5 implementations I found they're all pretty much the same
speed.

I changed the APIs (and ABIs) for the strong and weak checksums.
Strictly speaking I didn't need to do that. They're only called on
short strings of data, i.e. pathnames, so using int32_t and uint32_t
is ostensibly okay. My change is arguably a better, more general API
for this sort of thing. It's also what bit me when gerrit/jenkins
validation failed due to glusterfs segv-ing. (I didn't pay close enough
attention to the implementation of the weak checksum. But it forced me
to learn what gerrit/jenkins are doing and going forward I can do better
testing before submitting to gerrit.)

Now resubmitting with a BZ

Change-Id: I545fade1604e74fc68399894550229bd57a5e0df
BUG: 807718
Signed-off-by: Kaleb KEITHLEY 
Reviewed-on: http://review.gluster.com/3019
Tested-by: Gluster Build System 
Reviewed-by: Jeff Darcy