[pnfs] [PATCH 0/2] Update seqid and stateid handling to draft 13

[Muntz, Daniel]

I'm confused.  Are you saying the patches aren't appropriate because
there's an issue with a v4.1/v4.0 conflict (i.e., the patches are
breaking 4.0)?  Or are the patches breaking code where draft 13 does not
require the server to ignore seqid/stateids (there are several cases
called out in the diffs between draft 10 and 13 where ignoring is now
required).
 
   -Dan

________________________________

From: William A. (Andy) Adamson [mailto:andros at citi.umich.edu] 
Sent: Thursday, September 13, 2007 1:12 PM
To: Sager, Mike
Cc: pnfs at linux-nfs.org
Subject: Re: [pnfs] [PATCH 0/2] Update seqid and stateid handling to
draft 13


As I just emailed the list, draft-ietf-nfsv4-minorversion1-13.txt does
not change this behaviour from draft-ietf-nfsv4-minorversion1-10.txt.
See the "Vestigial Locking Infrastructure from V4" sections of both
drafts. 

So, these patches will not be applied at this time...


-->Andy


On 9/12/07, Sager, Mike < Mike.Sager at netapp.com
<mailto:Mike.Sager at netapp.com> > wrote: 

	Two patches to bring seqid and stateid handling up-to-date.  The
first basically updates the server to ignore the seqid.  The second
deals with the stateid's seqid (generation number).
	 
	Mike

	_______________________________________________
	pNFS mailing list
	pNFS at linux-nfs.org
	http://linux-nfs.org/cgi-bin/mailman/listinfo/pnfs
	


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