SSH: add protocol lock direction

Some protocols have to call the underlying functions without regard to
what exact state the socket signals. For example even if the socket says
"readable", the send function might need to be called while uploading,
or vice versa. This is the case for libssh2 based protocols: SCP and
SFTP and we now introduce a define to set those protocols and we make
the multi interface code aware of this concept.

This is another fix to make test 582 run properly.

1 files changed, 6 insertions, 0 deletions

diff --git a/lib/urldata.h b/lib/urldata.h
index 1d27d2626..2f7fe5e41 100644
--- a/lib/urldata.h
+++ b/lib/urldata.h
@@ -775,6 +775,12 @@ struct connectdata {
                           PROT_SFTP | PROT_SCP)
 #define PROT_DUALCHANNEL PROT_FTP /* these protocols use two connections */
 
+/* some protocols will have to call the underlying functions without regard to
+   what exact state the socket signals. IE even if the socket says "readable",
+   the send function might need to be called while uploading, or vice versa.
+*/
+#define PROT_LOCKEDBITS (PROT_SCP | PROT_SFTP)
+
   /* 'dns_entry' is the particular host we use. This points to an entry in the
      DNS cache and it will not get pruned while locked. It gets unlocked in
      Curl_done(). This entry will be NULL if the connection is re-used as then