-
Notifications
You must be signed in to change notification settings - Fork 780
0.23.30 release prep & 2575 backport #2576
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## rel-0.23 #2576 +/- ##
=========================================
Coverage 95.25% 95.25%
=========================================
Files 97 97
Lines 21767 21771 +4
=========================================
+ Hits 20734 20738 +4
Misses 1033 1033 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
42f18ec to
5435be3
Compare
ctz
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See also #2578
Benchmark resultsInstruction countsSignificant differencesClick to expand
Other differencesClick to expand
Wall-timeSignificant differencesThere are no significant wall-time differences Other differencesClick to expand
Additional informationCheckout details:
|
I updated the PR desc release notes to cover this backport as well assuming we'll merge it first. Suggested tweaks to the release notes addition welcome! |
|
See also #2580. I think it probably doesn't mention calling out in the release notes? |
After receiving close notify, the TLS stream ends. The receive buffer can contain additional junk data received past close notify record, which obviously cannot be interpreted anymore. However, `UnbufferedConnectionCommon::process_tls_records_common()` tried to interpret this junk data. Add a check for `has_received_close_notify` to prevent calling the deframer on junk data. Also update the test to test also with a longer junk data (original junk data didn't trigger the bug).
5435be3 to
786c1da
Compare
|
I think this is ready for merge & release if everyone is happy with the proposed release notes. |
|
This is a backport of #2575 to
rel-0.23to prepare a 0.23.30 release with the fix.Proposed release notes
Connection::complete_io()to yield aWouldBlockerror when both read/write operations are blocked.