iotssl_log_errors() should check if still safe to invoke logger
Description
Environment
Gerrit Reviews
Release Notes Description
blocks
Activity
CB robot March 28, 2024 at 5:46 AM
Build couchbase-server-7.2.5-7575 contains libcouchbase commit b6a6c0f with commit message:
https://couchbasecloud.atlassian.net/browse/CCBC-1603#icft=CCBC-1603: do not log if logger is not accessible in iotssl_log_errors
CB robot December 19, 2023 at 1:39 AM
Build couchbase-server-7.1.6-3969 contains libcouchbase commit b6a6c0f with commit message:
https://couchbasecloud.atlassian.net/browse/CCBC-1603#icft=CCBC-1603: do not log if logger is not accessible in iotssl_log_errors
CB robot August 31, 2023 at 8:45 AM
Build capella-analytics-1.0.0-1006 contains libcouchbase commit b6a6c0f with commit message:
https://couchbasecloud.atlassian.net/browse/CCBC-1603#icft=CCBC-1603: do not log if logger is not accessible in iotssl_log_errors
CB robot August 31, 2023 at 7:35 AM
Build couchbase-server-7.6.0-1438 contains libcouchbase commit b6a6c0f with commit message:
https://couchbasecloud.atlassian.net/browse/CCBC-1603#icft=CCBC-1603: do not log if logger is not accessible in iotssl_log_errors
CB robot August 23, 2023 at 3:01 PM
Build couchbase-server-8.0.0-1384 contains libcouchbase commit b6a6c0f with commit message:
https://couchbasecloud.atlassian.net/browse/CCBC-1603#icft=CCBC-1603: do not log if logger is not accessible in iotssl_log_errors
The IO callbacks might be called, when IO context has been closed already. This issue is related to https://couchbasecloud.atlassian.net/browse/CCBC-1568#icft=CCBC-1568, while it fixed the problem in many places, iotssl_log_errors still does not do the NULL check.