Re: [Nfs-ganesha-devel] Correct initialization sequence

Looking at the code, dupreq2_pkginit() only depends on Ganesha config processing to initialize few things, so it should be OK to call anytime after Ganesha config processing. Regards, Malahal. On Wed, Jan 31, 2018 at 8:00 AM, Pradeep wrote: > Hi Bill, > > Is it ok to

Re: [Nfs-ganesha-devel] Correct initialization sequence

reordering, I hope Matt On Tue, Jan 30, 2018 at 1:40 PM, Pradeep wrote: > Hello, > > It is possible to receive requests anytime after nfs_Init_svc() is > completed. We initialize several things in nfs_Init() after this. This could > lead to processing of incoming

Re: [Nfs-ganesha-devel] Is there a field in the SVCXPRT Ganesha can use

Restating this, the code is unified for tcp v4 and v3. It consults xid and the checksum, which I think is a correct intent. The slot-reply cache in 4.1+ is, we hope, the improved mechanism. Matt On Tue, Jan 30, 2018 at 9:45 AM, Matt Benjamin wrote: > I don't think that's

[Nfs-ganesha-devel] Correct initialization sequence

Hello, It is possible to receive requests anytime after nfs_Init_svc() is completed. We initialize several things in nfs_Init() after this. This could lead to processing of incoming requests racing with the rest of initialization (ex: dupreq2_pkginit()). Is it possible to re-order nfs_Init_svc()

[Nfs-ganesha-devel] Features board list

Hello all, As discussed in community call, I am sharing the feature board list: https://github.com/nfs-ganesha/nfs-ganesha/projects for nfs-ganesha 2.6 and 2.7. The aim is to use these boards to track the planned features for major release. The hope is that it will help community members to

[Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: Moving NFSv4 to POSIX ACL mapping code to a common code base

>From Sriram Patil : Sriram Patil has uploaded this change for review. ( https://review.gerrithub.io/397183 Change subject: Moving NFSv4 to POSIX ACL mapping code to a common code base .. Moving NFSv4 to

Re: [Nfs-ganesha-devel] Is there a field in the SVCXPRT Ganesha can use

innovations? ok. there's other innovation needed in the gss impl, that would be welcome as well Matt On Tue, Jan 30, 2018 at 9:50 AM, William Allen Simpson wrote: > On 1/30/18 9:36 AM, William Allen Simpson wrote: >> >> But the code is obscure, so I could be

Re: [Nfs-ganesha-devel] Is there a field in the SVCXPRT Ganesha can use

On 1/30/18 9:36 AM, William Allen Simpson wrote: But the code is obscure, so I could be missing something. Also, it bears repeating that the dupreq cache wasn't working for secure connections. Pre-V2.6 checksummed the ciphertext, which is by definition different on every request. We'd never

Re: [Nfs-ganesha-devel] Is there a field in the SVCXPRT Ganesha can use

I don't think that's the case. the behavior is distinct for v4 and v3 (which does not have clientids). DRC is bypassed for v4.1+ Matt On Tue, Jan 30, 2018 at 9:36 AM, William Allen Simpson wrote: > On 1/30/18 9:22 AM, William Allen Simpson wrote: >> >> On

Re: [Nfs-ganesha-devel] Is there a field in the SVCXPRT Ganesha can use

On 1/30/18 9:22 AM, William Allen Simpson wrote: On 1/29/18 3:32 PM, Frank Filz wrote: I haven't looked at how the SVCXPRT structure has changed, but if there's a field in there we can attach a Ganesha structure to that would be cool, or if not, if we could add one. There are two: xp_u1, and

Re: [Nfs-ganesha-devel] Is there a field in the SVCXPRT Ganesha can use

That sounds right, I figured we could reclaim xp_u1. Matt On Tue, Jan 30, 2018 at 9:22 AM, William Allen Simpson wrote: > On 1/29/18 3:32 PM, Frank Filz wrote: >> >> I haven't looked at how the SVCXPRT structure has changed, but if there's >> a >> field in there

Re: [Nfs-ganesha-devel] Is there a field in the SVCXPRT Ganesha can use

On 1/29/18 3:32 PM, Frank Filz wrote: I haven't looked at how the SVCXPRT structure has changed, but if there's a field in there we can attach a Ganesha structure to that would be cool, or if not, if we could add one. There are two: xp_u1, and xp_u2. Right now, Ganesha is using xp_u2 for dup

Re: [Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: Pullup ntirpc 1.6

On 01/30/2018 09:11 AM, William Allen Simpson wrote: On 1/29/18 2:27 PM, Daniel Gryniewicz wrote: On 01/29/2018 02:09 PM, William Allen Simpson wrote: On 1/29/18 1:13 PM, GerritHub wrote: Daniel Gryniewicz has uploaded this change for *review*. View Change

Re: [Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: Pullup ntirpc 1.6

On 1/29/18 2:27 PM, Daniel Gryniewicz wrote: On 01/29/2018 02:09 PM, William Allen Simpson wrote: On 1/29/18 1:13 PM, GerritHub wrote: Daniel Gryniewicz has uploaded this change for *review*. View Change Pullup ntirpc 1.6 (svc_vc) rearm after EAGAIN and