vtls: optimize the error handling in ssl_cf_connect()#19196
Closed
x2018 wants to merge 1 commit into
Closed
Conversation
…ence at first, then init peer and do connect
bagder
approved these changes
Oct 23, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
In lib/vtls/vtls.c:ssl_cf_connect(), an error path do not properly restore the cfilter.
This PR unifies its error handling.
By the way, as checking preferences is more lightweight than initing a peer, this PR also optimize the execution order: Check prefs at first to avoid unnecessary initialization for a peer when ssl_prefs_check fails.