Date: Wed, 09 Feb 2022 23:19:13 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 261291] ESX NFS4.1 client hangs, server never responds to EXCHANGE_ID/CREATE_SESSION Message-ID: <bug-261291-227-wlgOOB8dy8@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-261291-227@https.bugs.freebsd.org/bugzilla/> References: <bug-261291-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D261291 --- Comment #18 from commit-hook@FreeBSD.org --- A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=3D17a56f3fabdfacb62f6d8858643cdb186= 1c8c1b5 commit 17a56f3fabdfacb62f6d8858643cdb1861c8c1b5 Author: Rick Macklem <rmacklem@FreeBSD.org> AuthorDate: 2022-02-09 23:17:50 +0000 Commit: Rick Macklem <rmacklem@FreeBSD.org> CommitDate: 2022-02-09 23:17:50 +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. Reported by: asomers Tested by: asomers PR: 261291 MFC after: 1 week sys/fs/nfsserver/nfs_nfsdstate.c | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-261291-227-wlgOOB8dy8>