Re: [Nfs-ganesha-devel] only use of UDP client is NSM

2017-08-09 Thread Malahal Naineni 
This talks about xnfs, not sure how it is different from nfs though: Here
is a link that says UDP is mandatory for NSM (and TCP is optional).

http://pubs.opengroup.org/onlinepubs/9629799/chap11.htm

On Wed, Aug 9, 2017 at 9:28 PM, William Allen Simpson <
william.allen.simp...@gmail.com> wrote:

> On 8/8/17 11:46 PM, Malahal Naineni wrote:
>
>>  >> AFAICT from grep'ing the NFS documents, NFSv3 NSM *MUST* support TCP.
>>
>> As far as I know, there is only one version (version 1) of NSM protocol.
>> Let us not mix this with NFS protocol. Here is a wording I read from an NSM
>> document:
>>
>> "The NSM Protocol is required to support the UDP/IP transport protocol to
>> allow the NLM to operate. However, implementors may also choose to support
>> the TCP/IP transport protocol."
>>
>> Could you point (or send) me at that document?
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel

Re: [Nfs-ganesha-devel] only use of UDP client is NSM

2017-08-09 Thread Daniel Gryniewicz 

On 08/08/2017 10:34 PM, William Allen Simpson wrote:

On 8/8/17 1:58 PM, Daniel Gryniewicz wrote:

On 08/08/2017 01:17 PM, William Allen Simpson wrote:

NSM should be accessible by TCP.  Why are we using UDP?

Is there a downstream need?



Yes, there is a downstream need for NSM.


Would prefer folks answer the question asked.  I didn't ask about NSM.
Note the lack of a question mark

It very explicitly asked:

"Why are we using UDP? Is there a downstream need?"

AFAICT from grep'ing the NFS documents, NFSv3 NSM *MUST* support TCP.
We do not support NFSv2.  We should be using TCP.

Do we have a downstream need for NFSv2 support for NSM only?

If not, I'm going to drop this unsupported and frankly kludgy code.


NFSv3 supports UDP.  We support NFSv3.  Therefore we support UDP, for 
*all* of NFSv3.  I will not approve any patch that removes UDP support 
from Ganesha.  If the community prefers otherwise, so be it, but I 
believe UDP support is necessary.


Daniel

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel

Re: [Nfs-ganesha-devel] only use of UDP client is NSM

2017-08-08 Thread Frank Filz 
> I do not support dropping UDP.  Thanks.

I think there are NFS v3 clients out there that only use UDP for NLM...

Frank

> On Tue, Aug 8, 2017 at 10:34 PM, William Allen Simpson
>  wrote:
> > On 8/8/17 1:58 PM, Daniel Gryniewicz wrote:
> >>
> >> On 08/08/2017 01:17 PM, William Allen Simpson wrote:
> >>>
> >>> NSM should be accessible by TCP.  Why are we using UDP?
> >>>
> >>> Is there a downstream need?
> >>>
> >>
> >> Yes, there is a downstream need for NSM.
> >>
> > Would prefer folks answer the question asked.  I didn't ask about NSM.
> > Note the lack of a question mark
> >
> > It very explicitly asked:
> >
> > "Why are we using UDP? Is there a downstream need?"
> >
> > AFAICT from grep'ing the NFS documents, NFSv3 NSM *MUST* support
> TCP.
> > We do not support NFSv2.  We should be using TCP.
> >
> > Do we have a downstream need for NFSv2 support for NSM only?
> >
> > If not, I'm going to drop this unsupported and frankly kludgy code.
> >
> >
> > --
> >  Check out the vibrant tech community on one of the world's
> > most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> > ___
> > Nfs-ganesha-devel mailing list
> > Nfs-ganesha-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
> 
>

--
> Check out the vibrant tech community on one of the world's most engaging
> tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Nfs-ganesha-devel mailing list
> Nfs-ganesha-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel

Re: [Nfs-ganesha-devel] only use of UDP client is NSM

2017-08-08 Thread Matt Benjamin 
I do not support dropping UDP.  Thanks.

Matt

On Tue, Aug 8, 2017 at 10:34 PM, William Allen Simpson
 wrote:
> On 8/8/17 1:58 PM, Daniel Gryniewicz wrote:
>>
>> On 08/08/2017 01:17 PM, William Allen Simpson wrote:
>>>
>>> NSM should be accessible by TCP.  Why are we using UDP?
>>>
>>> Is there a downstream need?
>>>
>>
>> Yes, there is a downstream need for NSM.
>>
> Would prefer folks answer the question asked.  I didn't ask about NSM.
> Note the lack of a question mark
>
> It very explicitly asked:
>
> "Why are we using UDP? Is there a downstream need?"
>
> AFAICT from grep'ing the NFS documents, NFSv3 NSM *MUST* support TCP.
> We do not support NFSv2.  We should be using TCP.
>
> Do we have a downstream need for NFSv2 support for NSM only?
>
> If not, I'm going to drop this unsupported and frankly kludgy code.
>
>
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Nfs-ganesha-devel mailing list
> Nfs-ganesha-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel

Re: [Nfs-ganesha-devel] only use of UDP client is NSM

2017-08-08 Thread William Allen Simpson 

On 8/8/17 1:58 PM, Daniel Gryniewicz wrote:

On 08/08/2017 01:17 PM, William Allen Simpson wrote:

NSM should be accessible by TCP.  Why are we using UDP?

Is there a downstream need?



Yes, there is a downstream need for NSM.


Would prefer folks answer the question asked.  I didn't ask about NSM.
Note the lack of a question mark

It very explicitly asked:

"Why are we using UDP? Is there a downstream need?"

AFAICT from grep'ing the NFS documents, NFSv3 NSM *MUST* support TCP.
We do not support NFSv2.  We should be using TCP.

Do we have a downstream need for NFSv2 support for NSM only?

If not, I'm going to drop this unsupported and frankly kludgy code.

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel

Re: [Nfs-ganesha-devel] only use of UDP client is NSM

2017-08-08 Thread Niels de Vos 
On Tue, Aug 08, 2017 at 01:17:35PM -0400, William Allen Simpson wrote:
> Frank, Dominique tracked it down:
> 
> #0 0x4e2ea0 in calloc 
> (/export/nfs-ganesha/build/MainNFSD/ganesha.nfsd+0x4e2ea0)
> #1 0x5d0447 in gsh_calloc__ 
> /export/nfs-ganesha/src/include/abstract_mem.h:145:12
> #2 0x758f7eb6 in svc_dg_xprt_zalloc 
> /export/nfs-ganesha/src/libntirpc/src/svc_dg.c:101:27
> #3 0x758f7abc in svc_dg_xprt_setup 
> /export/nfs-ganesha/src/libntirpc/src/svc_dg.c:119:28
> #4 0x759009eb in svc_xprt_lookup 
> /export/nfs-ganesha/src/libntirpc/src/svc_xprt.c:165:4
> #5 0x758f7608 in svc_dg_ncreatef 
> /export/nfs-ganesha/src/libntirpc/src/svc_dg.c:139:9
> #6 0x758de453 in clnt_dg_ncreatef 
> /export/nfs-ganesha/src/libntirpc/src/clnt_dg.c:123:9
> #7 0x758e11c2 in clnt_dg_ncreate 
> /export/nfs-ganesha/src/libntirpc/ntirpc/rpc/clnt.h:505:10
> #8 0x758e0e64 in clnt_tli_ncreate 
> /export/nfs-ganesha/src/libntirpc/src/clnt_generic.c:383:8
> #9 0x758f32d7 in getclnthandle 
> /export/nfs-ganesha/src/libntirpc/src/rpcb_clnt.c:378:7
> #10 0x758f2622 in __rpcb_findaddr_timed 
> /export/nfs-ganesha/src/libntirpc/src/rpcb_clnt.c:651:13
> #11 0x758e0a0f in clnt_tp_ncreate_timed 
> /export/nfs-ganesha/src/libntirpc/src/clnt_generic.c:287:3
> #12 0x758e08a2 in clnt_ncreate_timed 
> /export/nfs-ganesha/src/libntirpc/src/clnt_generic.c:207:10
> #13 0x758e099d in clnt_ncreate 
> /export/nfs-ganesha/src/libntirpc/src/clnt_generic.c:156:10
> #14 0x844a3a in gsh_clnt_create 
> /export/nfs-ganesha/src/RPCAL/rpc_tools.c:487:9
> #15 0x71d311 in nsm_connect 
> /export/nfs-ganesha/src/Protocols/NLM/nsm.c:55:13
> #16 0x722ae9 in nsm_unmonitor_all 
> /export/nfs-ganesha/src/Protocols/NLM/nsm.c:252:7
> #17 0x5de964 in nfs_start 
> /export/nfs-ganesha/src/MainNFSD/nfs_init.c:939:3
> #18 0x51c685 in main /export/nfs-ganesha/src/MainNFSD/nfs_main.c:489:2
> #19 0x74df2400 in __libc_start_main (/lib64/libc.so.6+0x20400)
> 
> NSM should be accessible by TCP.  Why are we using UDP?
> 
> Is there a downstream need?

Gluster/NFS (v3) only has UDP support for the MOUNT protocol. This is
something that several customers use and expect to be available. I do
not think we should encourage the use of UDP for NFS, removing it or at
least disable it downstream should be ok.

HTH,
Niels

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel

Re: [Nfs-ganesha-devel] only use of UDP client is NSM

2017-08-08 Thread Daniel Gryniewicz 

On 08/08/2017 01:17 PM, William Allen Simpson wrote:

Frank, Dominique tracked it down:

 #0 0x4e2ea0 in calloc 
(/export/nfs-ganesha/build/MainNFSD/ganesha.nfsd+0x4e2ea0)
 #1 0x5d0447 in gsh_calloc__ 
/export/nfs-ganesha/src/include/abstract_mem.h:145:12
 #2 0x758f7eb6 in svc_dg_xprt_zalloc 
/export/nfs-ganesha/src/libntirpc/src/svc_dg.c:101:27
 #3 0x758f7abc in svc_dg_xprt_setup 
/export/nfs-ganesha/src/libntirpc/src/svc_dg.c:119:28
 #4 0x759009eb in svc_xprt_lookup 
/export/nfs-ganesha/src/libntirpc/src/svc_xprt.c:165:4
 #5 0x758f7608 in svc_dg_ncreatef 
/export/nfs-ganesha/src/libntirpc/src/svc_dg.c:139:9
 #6 0x758de453 in clnt_dg_ncreatef 
/export/nfs-ganesha/src/libntirpc/src/clnt_dg.c:123:9
 #7 0x758e11c2 in clnt_dg_ncreate 
/export/nfs-ganesha/src/libntirpc/ntirpc/rpc/clnt.h:505:10
 #8 0x758e0e64 in clnt_tli_ncreate 
/export/nfs-ganesha/src/libntirpc/src/clnt_generic.c:383:8
 #9 0x758f32d7 in getclnthandle 
/export/nfs-ganesha/src/libntirpc/src/rpcb_clnt.c:378:7
 #10 0x758f2622 in __rpcb_findaddr_timed 
/export/nfs-ganesha/src/libntirpc/src/rpcb_clnt.c:651:13
 #11 0x758e0a0f in clnt_tp_ncreate_timed 
/export/nfs-ganesha/src/libntirpc/src/clnt_generic.c:287:3
 #12 0x758e08a2 in clnt_ncreate_timed 
/export/nfs-ganesha/src/libntirpc/src/clnt_generic.c:207:10
 #13 0x758e099d in clnt_ncreate 
/export/nfs-ganesha/src/libntirpc/src/clnt_generic.c:156:10
 #14 0x844a3a in gsh_clnt_create 
/export/nfs-ganesha/src/RPCAL/rpc_tools.c:487:9
 #15 0x71d311 in nsm_connect 
/export/nfs-ganesha/src/Protocols/NLM/nsm.c:55:13
 #16 0x722ae9 in nsm_unmonitor_all 
/export/nfs-ganesha/src/Protocols/NLM/nsm.c:252:7
 #17 0x5de964 in nfs_start 
/export/nfs-ganesha/src/MainNFSD/nfs_init.c:939:3

 #18 0x51c685 in main /export/nfs-ganesha/src/MainNFSD/nfs_main.c:489:2
 #19 0x74df2400 in __libc_start_main (/lib64/libc.so.6+0x20400)

NSM should be accessible by TCP.  Why are we using UDP?

Is there a downstream need?



Yes, there is a downstream need for NSM.

Daniel

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel

Re: [Nfs-ganesha-devel] only use of UDP client is NSM

2017-08-08 Thread Matt Benjamin 
Hi Bill,

While NFSv3 supports TCP, UDP is also supported.

Matt

On Tue, Aug 8, 2017 at 1:17 PM, William Allen Simpson
 wrote:
> Frank, Dominique tracked it down:
>
> #0 0x4e2ea0 in calloc
> (/export/nfs-ganesha/build/MainNFSD/ganesha.nfsd+0x4e2ea0)
> #1 0x5d0447 in gsh_calloc__
> /export/nfs-ganesha/src/include/abstract_mem.h:145:12
> #2 0x758f7eb6 in svc_dg_xprt_zalloc
> /export/nfs-ganesha/src/libntirpc/src/svc_dg.c:101:27
> #3 0x758f7abc in svc_dg_xprt_setup
> /export/nfs-ganesha/src/libntirpc/src/svc_dg.c:119:28
> #4 0x759009eb in svc_xprt_lookup
> /export/nfs-ganesha/src/libntirpc/src/svc_xprt.c:165:4
> #5 0x758f7608 in svc_dg_ncreatef
> /export/nfs-ganesha/src/libntirpc/src/svc_dg.c:139:9
> #6 0x758de453 in clnt_dg_ncreatef
> /export/nfs-ganesha/src/libntirpc/src/clnt_dg.c:123:9
> #7 0x758e11c2 in clnt_dg_ncreate
> /export/nfs-ganesha/src/libntirpc/ntirpc/rpc/clnt.h:505:10
> #8 0x758e0e64 in clnt_tli_ncreate
> /export/nfs-ganesha/src/libntirpc/src/clnt_generic.c:383:8
> #9 0x758f32d7 in getclnthandle
> /export/nfs-ganesha/src/libntirpc/src/rpcb_clnt.c:378:7
> #10 0x758f2622 in __rpcb_findaddr_timed
> /export/nfs-ganesha/src/libntirpc/src/rpcb_clnt.c:651:13
> #11 0x758e0a0f in clnt_tp_ncreate_timed
> /export/nfs-ganesha/src/libntirpc/src/clnt_generic.c:287:3
> #12 0x758e08a2 in clnt_ncreate_timed
> /export/nfs-ganesha/src/libntirpc/src/clnt_generic.c:207:10
> #13 0x758e099d in clnt_ncreate
> /export/nfs-ganesha/src/libntirpc/src/clnt_generic.c:156:10
> #14 0x844a3a in gsh_clnt_create
> /export/nfs-ganesha/src/RPCAL/rpc_tools.c:487:9
> #15 0x71d311 in nsm_connect
> /export/nfs-ganesha/src/Protocols/NLM/nsm.c:55:13
> #16 0x722ae9 in nsm_unmonitor_all
> /export/nfs-ganesha/src/Protocols/NLM/nsm.c:252:7
> #17 0x5de964 in nfs_start
> /export/nfs-ganesha/src/MainNFSD/nfs_init.c:939:3
> #18 0x51c685 in main /export/nfs-ganesha/src/MainNFSD/nfs_main.c:489:2
> #19 0x74df2400 in __libc_start_main (/lib64/libc.so.6+0x20400)
>
> NSM should be accessible by TCP.  Why are we using UDP?
>
> Is there a downstream need?
>
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Nfs-ganesha-devel mailing list
> Nfs-ganesha-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel

[Nfs-ganesha-devel] only use of UDP client is NSM

2017-08-08 Thread William Allen Simpson 

Frank, Dominique tracked it down:

#0 0x4e2ea0 in calloc 
(/export/nfs-ganesha/build/MainNFSD/ganesha.nfsd+0x4e2ea0)
#1 0x5d0447 in gsh_calloc__ 
/export/nfs-ganesha/src/include/abstract_mem.h:145:12
#2 0x758f7eb6 in svc_dg_xprt_zalloc 
/export/nfs-ganesha/src/libntirpc/src/svc_dg.c:101:27
#3 0x758f7abc in svc_dg_xprt_setup 
/export/nfs-ganesha/src/libntirpc/src/svc_dg.c:119:28
#4 0x759009eb in svc_xprt_lookup 
/export/nfs-ganesha/src/libntirpc/src/svc_xprt.c:165:4
#5 0x758f7608 in svc_dg_ncreatef 
/export/nfs-ganesha/src/libntirpc/src/svc_dg.c:139:9
#6 0x758de453 in clnt_dg_ncreatef 
/export/nfs-ganesha/src/libntirpc/src/clnt_dg.c:123:9
#7 0x758e11c2 in clnt_dg_ncreate 
/export/nfs-ganesha/src/libntirpc/ntirpc/rpc/clnt.h:505:10
#8 0x758e0e64 in clnt_tli_ncreate 
/export/nfs-ganesha/src/libntirpc/src/clnt_generic.c:383:8
#9 0x758f32d7 in getclnthandle 
/export/nfs-ganesha/src/libntirpc/src/rpcb_clnt.c:378:7
#10 0x758f2622 in __rpcb_findaddr_timed 
/export/nfs-ganesha/src/libntirpc/src/rpcb_clnt.c:651:13
#11 0x758e0a0f in clnt_tp_ncreate_timed 
/export/nfs-ganesha/src/libntirpc/src/clnt_generic.c:287:3
#12 0x758e08a2 in clnt_ncreate_timed 
/export/nfs-ganesha/src/libntirpc/src/clnt_generic.c:207:10
#13 0x758e099d in clnt_ncreate 
/export/nfs-ganesha/src/libntirpc/src/clnt_generic.c:156:10
#14 0x844a3a in gsh_clnt_create 
/export/nfs-ganesha/src/RPCAL/rpc_tools.c:487:9
#15 0x71d311 in nsm_connect 
/export/nfs-ganesha/src/Protocols/NLM/nsm.c:55:13
#16 0x722ae9 in nsm_unmonitor_all 
/export/nfs-ganesha/src/Protocols/NLM/nsm.c:252:7
#17 0x5de964 in nfs_start /export/nfs-ganesha/src/MainNFSD/nfs_init.c:939:3
#18 0x51c685 in main /export/nfs-ganesha/src/MainNFSD/nfs_main.c:489:2
#19 0x74df2400 in __libc_start_main (/lib64/libc.so.6+0x20400)

NSM should be accessible by TCP.  Why are we using UDP?

Is there a downstream need?

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel