Add sk_new_reserve support

This is a specific 1.1.1 change; do not squash if the chacha
prioritization code is to be backported

Reviewed-by: Paul Dale <paul.dale@oracle.com>
Reviewed-by: Tim Hudson <tjh@openssl.org>
Reviewed-by: Andy Polyakov <appro@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/4436)

diff --git a/ssl/s3_lib.c b/ssl/s3_lib.c
index c063fff87a25a23894a0c351f566dd22b2464f28..e71373d2bfe166df2cf29dc46bb0624ba7c66cf8 100644 (file)
--- a/ssl/s3_lib.c
+++ b/ssl/s3_lib.c
@@ -4173,7 +4173,7 @@ const SSL_CIPHER *ssl3_choose_cipher(SSL *s, STACK_OF(SSL_CIPHER) *clnt,
                     }
                 }
                 if (found) {
-                    prio_chacha = sk_SSL_CIPHER_new_null();
+                    prio_chacha = sk_SSL_CIPHER_new_reserve(NULL, num);
                     /* if reserve fails, then there's likely a memory issue */
                     if (prio_chacha != NULL) {
                         /* Put all ChaCha20 at the top, starting with the one we just found */