[openssl] openssl-3.0 update

[tomas at openssl.org]

The branch openssl-3.0 has been updated
       via  4f4711c7657396239ba9b9e5a7149e3cdcafe2e4 (commit)
      from  fa885e4ba153b6be3e446c8f323762482cef92ae (commit)


- Log -----------------------------------------------------------------
commit 4f4711c7657396239ba9b9e5a7149e3cdcafe2e4
Author: Tomas Mraz <tomas at openssl.org>
Date:   Thu Oct 7 11:10:19 2021 +0200

    doc: OPENSSL_CORE_CTX should never be cast to OSSL_LIB_CTX
    
    Reviewed-by: Matt Caswell <matt at openssl.org>
    (Merged from https://github.com/openssl/openssl/pull/16771)
    
    (cherry picked from commit 2b80a7490d5008fa40417b804ea16e8fee13d93d)

-----------------------------------------------------------------------

Summary of changes:
 doc/man7/provider-base.pod | 10 +++++++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/doc/man7/provider-base.pod b/doc/man7/provider-base.pod
index d1e26baa11..0005dc7181 100644
--- a/doc/man7/provider-base.pod
+++ b/doc/man7/provider-base.pod
@@ -220,10 +220,14 @@ the thread that is stopping and gets passed the provider context as an
 argument. This may be useful to perform thread specific clean up such as
 freeing thread local variables.
 
-core_get_libctx() retrieves the library context in which the library
+core_get_libctx() retrieves the core context in which the library
 object for the current provider is stored, accessible through the I<handle>.
-This may sometimes be useful if the provider wishes to store a
-reference to its context in the same library context.
+This function is useful only for built-in providers such as the default
+provider. Never cast this to OSSL_LIB_CTX in a provider that is not
+built-in as the OSSL_LIB_CTX of the library loading the provider might be
+a completely different structure than the OSSL_LIB_CTX of the library the
+provider is linked to. Use  L<OSSL_LIB_CTX_new_child(3)> instead to obtain
+a proper library context that is linked to the application library context.
 
 core_new_error(), core_set_error_debug() and core_vset_error() are
 building blocks for reporting an error back to the core, with