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.
