Date: Tue, 30 Mar 2021 14:22:54 +1100 From: Kubilay Kocak <koobs@FreeBSD.org> To: Rick Macklem <rmacklem@uoguelph.ca>, freebsd-stable <freebsd-stable@freebsd.org> Subject: Re: FreeBSD NFSv4.1/4.2 server is broken when Linux mounts use "nconnects" Message-ID: <db4a5d0a-9d30-96de-1db2-f498257add6e@FreeBSD.org> In-Reply-To: <YQXPR0101MB0968CD19A33C3F03FFD7F4F4DD7E9@YQXPR0101MB0968.CANPRD01.PROD.OUTLOOK.COM> References: <YQXPR0101MB0968CD19A33C3F03FFD7F4F4DD7E9@YQXPR0101MB0968.CANPRD01.PROD.OUTLOOK.COM>
next in thread | previous in thread | raw e-mail | index | archive | help
On 30/03/2021 8:52 am, Rick Macklem wrote: > Hi, > > The FreeBSD NFS server is broken when handling multiple > connections for NFSv4.1/4.2. Whats the version scope for this issue? If a regression in 12.x 13.x, adding to RELNOTES and ERRATA would be great > It incorrectly binds the back channel to a new connection > when is sees an RPC with Sequence in it (almost all RPCs) > and might send a callback on the wrong connection. > > I have a fix, but it won't be in a release until 12.3/13.1. > It can be found in Bugzilla PR#254560. > > In the meantime, avoid using the "nconnects" option > on Linux client mounts. > > Thanks go to Ben Coddington @redhat for diagnosing > this and testing the patch. > > Sorry about the breakage, rick > ps: It was done intentionally long ago, when clients > did not do BindConnectionToSession and then slipped > through the cracks.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?db4a5d0a-9d30-96de-1db2-f498257add6e>