Skip to content

Conversation

@icing
Copy link
Contributor

@icing icing commented Feb 8, 2025

Keeping the relevant 'ssl_scache' in 'data->state' leads to problems when the owner of the cache is cleaned up and this reference is left dangling.

Remove the ref entirely and always find the ssl_scache at the curren share or multi.

Folded in #16260 to verify this fixes the bug with a dangling reference when an easy handle is used with easy_perform first and in a multi_perform after.

refs #16236

Keeping the relevant 'ssl_scache' in 'data->state' leads to
problems when the owner of the cache is cleaned up and this
reference is left dangling.

Remove the ref entirely and always find the ssl_scache at
the curren share or multi.

Folded in curl#16260 to verify this fixes the bug with a dangling
reference when an easy handle is used with easy_perform first
and in a multi_perform after.

refs curl#16236
@github-actions github-actions bot added the tests label Feb 8, 2025
@bagder bagder closed this in 242a143 Feb 8, 2025
pps83 pushed a commit to pps83/curl that referenced this pull request Apr 26, 2025
Keeping the relevant 'ssl_scache' in 'data->state' leads to problems
when the owner of the cache is cleaned up and this reference is left
dangling.

Remove the ref entirely and always find the ssl_scache at the current
share or multi.

Folded in curl#16260 (test 3208) to verify this fixes the bug with a
dangling reference when an easy handle is used with easy_perform first
and in a multi_perform after.

Ref: curl#16236
Closes curl#16261
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Development

Successfully merging this pull request may close these issues.

2 participants