Date: Thu, 25 Mar 2021 22:09:43 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 254560] NFSv4.1 server broken when mounted by Linux using nconnects Message-ID: <bug-254560-227-7sDSPoVKgG@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-254560-227@https.bugs.freebsd.org/bugzilla/> References: <bug-254560-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=3D254560 Rick Macklem <rmacklem@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bugs@FreeBSD.org |rmacklem@FreeBSD.org Status|New |Open --- Comment #1 from Rick Macklem <rmacklem@FreeBSD.org> --- Created attachment 223584 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D223584&action= =3Dedit fix NFSv4.1 server so that it does not bind a new conn to backchannel The NFSv4.1 (and 4.2 on 13) server incorrectly binds a new TCP connection to the backchannel when first used by an RPC with Sequence. RFC5661 specified that it should only bind to the fore channel. This was done because early clients (including FreeBSD) did not do the required BindConnectionToSession RPC. Unfortunately, this breaks the Linux client when the "nconnects" mount option is used, since the server may do a callback on the incorrect TCP connection. This patch converts the server behaviour to that required by the RFC. Until this patch is applied to the server, the "nconnects" mount option should not be used. --=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-254560-227-7sDSPoVKgG>