On Wed, Jan 19, 2022 at 9:49 PM Ronnie Sahlberg <lsahlber@xxxxxxxxxx> wrote: > > RHBZ: 2008434 > > If we try to perform multiple concurrent mounts ot the same server we might > end up in a situation where: > Thread #1 Thread #2 > creates TCP connection > Issues NegotiateProtocol > ... Pick the TCP connection for Thread #1 > Issue a new NegotiateProtocol checking server->tcpStatus state should prevent this situation no? > which then leads to the the server kills off the session. > There are also other a similar race where several threads ending up > withe their own unique tcp connection that all go to the same server structure .... > > The most straightforward way to fix these races with concurrent mounts are to serialize > them. I.e. only allow one mount to be in progress at a time.
