-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Fix SCTP fragment handling #8837
base: maint-26
Are you sure you want to change the base?
Fix SCTP fragment handling #8837
Conversation
CT Test Results 3 files 143 suites 46m 40s ⏱️ Results for commit 73e1aa1. ♻️ This comment has been updated with latest results. To speed up review, make sure that you have read Contributing to Erlang/OTP and that all checks pass. See the TESTING and DEVELOPMENT HowTo guides for details about how to run test locally. Artifacts// Erlang/OTP Github Action Bot |
Getting ERRNO_BLOCK immediately could cause a buffer with message head to be wasted since it was forgotten that there was valid data in it.
Don't used the async return value functions except for TCP that would block. All other cases are synchronous so return the result (ok or {ok,AssocId}) directly from port control.
73e1aa1
to
620fab3
Compare
Now rebased onto OTP-26.2.5, current OTP 26 patch base. |
0427f24
to
ea4be99
Compare
Getting ERRNO_BLOCK immediately could cause a buffer with message head to be wasted since it was forgotten that there was valid data in it.