From cb38052b3a3e4eda010f5b9893292921493eb890 Mon Sep 17 00:00:00 2001 From: =?utf8?q?Bodo=20M=C3=B6ller?= Date: Mon, 18 Dec 2000 09:18:22 +0000 Subject: [PATCH] Comment correction. --- crypto/ex_data.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/crypto/ex_data.c b/crypto/ex_data.c index 3898c33f86..ff32ad5be6 100644 --- a/crypto/ex_data.c +++ b/crypto/ex_data.c @@ -4,8 +4,10 @@ * This is not thread-safe, nor can it be changed to become thread-safe * without changing various function prototypes and using a lot of locking. * Luckily, it's not really used anywhere except in ssl_verify_cert_chain - * via SSL_get_ex_data_X509_STORE_CTX_idx (ssl/ssl_cert.c), where - * new_func, dup_func, and free_func all are 0. + * via SSL_get_ex_data_X509_STORE_CTX_idx (ssl/ssl_cert.c), + * where new_func, dup_func, and free_func all are 0, and in + * hwcrhk_init (crypto/engine/hw_ncipher.c), which is hopefully only + * ever used during program initialization. * * Any multi-threaded application crazy enough to use ex_data for its own * purposes had better make sure that SSL_get_ex_data_X509_STORE_CTX_idx -- 2.34.1