[Bug 261291] ESX NFS4.1 client hangs, server never responds to EXCHANGE_ID/CREATE_SESSION

From: <bugzilla-noreply_at_freebsd.org>
Date: Tue, 08 Feb 2022 23:47:46 UTC

--- Comment #15 from Rick Macklem <rmacklem@FreeBSD.org> ---
Well, deciding what the correct error is can be fun.
Here's the definition of NFS4ERR_SEQ_MISORDERED
in RFC5661:  NFS4ERR_SEQ_MISORDERED (Error Code 10063)

   The requester sent a Sequence operation with an invalid sequence ID.

It seems to indicate the error is specifically for the Sequence operation.

But, it does appear that you are correct, since in the implementation
of CREATE_SESSION, it talks about a single slot session just for
it is not correct.

I'll come up with a patch for this and attach it to this PR, but I
doubt it will fix this problem.

nfsrevoke causes the sever to reply NFS4ERR_ADMIN_REVOKED when
the client ID is referenced by the client. This probably causes the
client to throw away its notion of the client ID and then I suspect
it gets the seqid in CREATE_SESSION correct.
(Looking at the packet trace for this case could be interesting.;-)

You are receiving this mail because:
You are the assignee for the bug.