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

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261291

--- Comment #22 from commit-hook@FreeBSD.org ---
A commit in branch stable/12 references this bug:

URL:
https://cgit.FreeBSD.org/src/commit/?id=95e95764918f97112bb05282d62d9777b706c2fb

commit 95e95764918f97112bb05282d62d9777b706c2fb
Author:     Rick Macklem <rmacklem@FreeBSD.org>
AuthorDate: 2022-02-09 23:17:50 +0000
Commit:     Rick Macklem <rmacklem@FreeBSD.org>
CommitDate: 2022-02-16 22:59:41 +0000

    nfsd: Reply NFSERR_SEQMISORDERED for bogus seqid argument

    The ESXi NFSv4.1 client bogusly sends the wrong value
    for the csa_sequence argument for a Create_session operation.
    RFC8881 requires this value to be the same as the sequence
    reply from the ExchangeID operation most recently done for
    the client ID.

    Without this patch, the server replies NFSERR_STALECLIENTID,
    which is the correct response for an NFSv4.0 SetClientIDConfirm
    but is not the correct error for NFSv4.1/4.2, which is
    specified as NFSERR_SEQMISORDERED in RFC8881.
    This patch fixes this.

    This change does not fix the issue reported in the PR, where
    the ESXi client loops, attempting ExchangeID/Create_session
    repeatedly.

    PR:     261291

    (cherry picked from commit 17a56f3fabdfacb62f6d8858643cdb1861c8c1b5)

 sys/fs/nfsserver/nfs_nfsdstate.c | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

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