[nfsv4] seqids after changing slot table size

[Jeff Layton <[e-mail]>]

We're having a bit of a debate on the linux-nfs mailing list. The
question centers around this statement in section 2.10.6.1 in RFC 8881:

A slot contains a sequence ID and the cached reply corresponding to the
request sent with that sequence ID. The sequence ID is a 32-bit
unsigned value, and is therefore in the range 0..0xFFFFFFFF (232 - 1).
The first time a slot is used, the requester MUST specify a sequence ID
of one (Section 18.36). Each time a slot is reused, the request MUST
specify a sequence ID that is one greater than that of the previous
request on the slot. If the previous sequence ID was 0xFFFFFFFF, then
the next request for the slot MUST have the sequence ID set to zero
(i.e., (232 - 1) + 1 mod 232). 


...in particular, if the size of the slot table shrinks and then grows
again, do the reinstated slots need to retain their old seqid, or
should they be reinitialized at "1"?

By way of example:

Say the slot table size is 8. The acceptor shrinks that to 4, and then
later grows the slot table again to 8. When it grows from 4 to 8,
should the seqids for the last 4 slots be reset to "1"?

Thanks,
-- 
Jeff Layton <[e-mail]>