[pnfs] October Bakeathon and Vestigial Locking Infrastructure FromV4.0

[Sager, Mike]

Hi Andy,
 
Section 18.10.4 of Draft 13 has this: "The client field of the lock
owner, and all seqid values in the arguments MAY be any value and MUST
be ignored by the server"  which is different from that of Draft 10.
For the case described in 8.8 below, the patched code distinguishes
between 4.0 and 4.1, so I think both cases are covered.
 
Mike

	-----Original Message-----
	From: William A. (Andy) Adamson [mailto:andros at citi.umich.edu] 
	Sent: Thursday, September 13, 2007 1:09 PM
	To: NFSv4
	Cc: pnfs at linux-nfs.org
	Subject: [pnfs] October Bakeathon and Vestigial Locking
Infrastructure FromV4.0
	
	
	Just a note that draft-ietf-nfsv4-minorversion1-13.txt has not
changed the draft-ietf-nfsv4-minorversion10.txt language concerning the
requriement to zero sequence id's and client id's in existing operations
related to locking (OPEN, LOCK, LOCKU, etc).
	
	Since the October Bakeathon uses
draft-ietf-nfsv4-minorversion1-13.txt, we expect this behaviour. Maybe I
missed something - but I thought that at the Austin bakeathon it was
decided that the server could ignore vestigial locking sequence id and
client ids....
	
	-->Andy 
	
	>From draft-ietf-nfsv4-minorversion1-13.txt,
	8.8.  Vestigial Locking Infrastructure From V4.0
	
	          .......................
	
	   Also, there are a number of fields, present in existing
operations
	
	
	
	Shepler, et al.          Expires January 2, 2008
[Page 160]
	^L
	Internet-Draft            NFSv4 Minor Version 1
July 2007
	
	
	   related to locking that have no use in minor version one.
They were
	   used in minor version zero to perform functions now provided
in a
	   different fashion.
	
	   o  Sequence ids used to sequence requests for a given
state-owner and
	      to provide retry protection, now provided via sessions.
	
	   o  Client IDs used to identify the client associated with a
given
	      request.  Client identification is now available using the
client
	      ID associated with the current session, without needing an
	      explicit client ID field.
	
	   Such vestigial fields in existing operations should be set by
the
	   client to zero.  When they are not, the server MUST return an
	   NFS4ERR_INVAL error.
	
	
	

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://linux-nfs.org/pipermail/pnfs/attachments/20070913/5ae52eda/attachment.htm