Re: [nfsv4] CLIENTID race condition during server GRACE.

Next message: Robert Gordon: "[nfsv4] Minor Versioning."
Previous message: Stevan Steve Allen: "Re: [nfsv4] CLIENTID race condition during server GRACE."
In reply to: Stevan Steve Allen: "Re: [nfsv4] CLIENTID race condition during server GRACE."

spencer.shepler@sun.com

Date: Mon, 17 Jan 2005 17:56:45 -0600
From: Spencer Shepler <spencer.shepler@sun.com>
Subject: Re: [nfsv4] CLIENTID race condition during server GRACE.
Message-ID: <20050117235645.GC104782@nfsclient.central.sun.com>

On Mon, Stevan Steve Allen wrote:
> 
> 
> 
> 
> - On Mon, Jan 17, 2005 at 01:02:50PM -0800, Stevan Steve Allen wrote:
> -> RFC section 8.1.1 discusses ways to generate a unique CLIENT ID.
> -> SETCLIENTID discusses the use of credentials to detect a conflicting
> CLIENT
> -> ID when a client lease is active.  If the NFS server restarts, the
> -> credential relationship is lost.
> 
> On Mon, Jan 17, 2005, Bruce wrote:
> -Can't the server store the principal that did the setclientid in stable
> -storage?
> -b.
> Not in our current server design. I first wanted to confirm the protocol
> does not address this issue and what, if anything, other platforms are
> doing or decided on regarding the race condition.

If the server is offering a grace period to its clients, then it must
use some form of stable storage for reasons described in section 8.6.3.
No stable storage usage means no grace period.

If there is no grace period, not sure I see any race condition with
SETCLIENTID other than the normal collision that can occur.

Spencer

_______________________________________________
nfsv4 mailing list
nfsv4@ietf.org
https://www1.ietf.org/mailman/listinfo/nfsv4