extmod/modtls_mbedtls: Do gc_collect and retry ssl_init on any error. #17750
+1
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Contrary to the docs, mbedtls can return more than just MBEDTLS_ERR_SSL_ALLOC_FAILED when
mbedtls_ssl_setup()
fails. At least MBEDTLS_ERR_MD_ALLOC_FAILED was also seen on ESP32_GENERIC, but there could possibly be other error codes.To cover all these codes, just check if
ret
is non-0, and in that case do agc_collect()
and retry the init.Testing
Tested on ESP32_GENERIC with IDF 5.4.2, running
tests/extmod/tls_noleak.py
. Prior to the change here that test would fail if the board was connected to WiFi. With the change here the test passes.Trade-offs and Alternatives
Could just check for the additional MBEDTLS_ERR_MD_ALLOC_FAILED code, but IMO checking for
ret != 0
is more robust. The only sensible reason formbedtls_ssl_setup()
to fail is an out-of-memory error.