Issue171

Title Race example incorrect
Priority required Status resolved-edit-complete
Superseder Nosy List mre, spencer.shepler
Assigned To spencer.shepler Topics WGLASTCALL

Created on 2008-01-12.22:08:14 by mre, last changed 2008-01-12.23:06:19 by mre.

Messages
msg580 (view) Author: mre Date: 2008-01-12.23:05:26
Index: nfsv41_middle_pnfs.xml
===================================================================
RCS file: /cvs/stdk/NFSv41/nfsv41_middle_pnfs.xml,v
retrieving revision 1.66
retrieving revision 1.67
msg579 (view) Author: mre Date: 2008-01-12.22:08:14
The spec says.

``After the layout stateid is established, the "seqid" is incremented by the
server in each subsequent LAYOUTGET and LAYOUTRETURN response, and in each
CB_LAYOUTRECALL request. When the client fully processes the response to a
LAYOUTGET or LAYOUTRETURN, or fully processes the arguments of a
CB_LAYOUTRECALL, it MUST use the seqid of the stateid of the reply from
LAYOUTGET and LAYOUTRETURN, or the stateid in the arguments of CB_LAYOUTRECALL,
the client MUST use the seqid on subsequent calls to LAYOUTGET or LAYOUTRETURN. ''

However, in reading this, I see that 

> >    Note
> >    that in the first case, the "seqid" in the layout stateid of the
> >    recall is one greater than what the client has recorded and in
> the
> >    second case, the "seqid" is equal to what the client has
> recorded.

is wrong, because CB_LAYOUTRECALL increments the seqid.

Instead, it should be:

   Note that in the first case, the "seqid" in the layout stateid of the
   recall is *two* greater than what the client has recorded and in the
   second case, the "seqid" is *one* greater than what the client has recorded.
History
Date User Action Args
2008-01-12 23:06:19mresettopic: + WGLASTCALL
2008-01-12 23:05:47mresetassignedto: mre -> spencer.shepler
nosy: + spencer.shepler
2008-01-12 23:05:37mresetstatus: need-text -> resolved-edit-complete
2008-01-12 23:05:26mresetmessages: + msg580
2008-01-12 22:08:14mrecreate