Received-SPF: pass (google.com: best guess record for domain of linux-nfs-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
From:   Olga Kornievskaia <aglo@umich.edu>
Date:   Wed, 29 Jan 2020 12:12:12 -0500
Message-ID: <CAN-5tyGoKOQzPHjTikO4ScPGe7eyob5pLOH7JM3MfgFG1W7eDQ@mail.gmail.com>
Subject: question about nconnect implementation
To:     linux-nfs <linux-nfs@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-nfs-owner@vger.kernel.org
Precedence: bulk

Hi Trond,

Correct me if I'm wrong but I believe currently the client will never
bind new (nconnect) connections to an existing session until it gets
an error CONN_NOT_BOUND_TO_SESSION, is that correct?
nfs4_proc_bind_conn_to_session() that iterates over the transports is
only called nfs4state's nfs4_bind_conn_to_session when cl_stat's flag
of BIND_CONN_TO_SESSION is set and it's set on error handling of
CONN_NOT_BOUND.

Is the reason client not explicitly sending BIND_CONN_TO_SESSION
before sending other operations is because client (implements)
specifies "no state protection" for the client? And according to the
spec if no state protection is used then just sending a SEQUENCE on a
new connection is sufficient to create an association between that
connection and the session?

Thank you.