Add I/O safety to sockopt and some socket functions #1915
Merged
Conversation
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
Member
asomers
commented
Dec 5, 2022
asomers
commented
- socket
- socketpair
- listen
- setsockopt
- getsockopt
This was referenced Dec 5, 2022
asomers
force-pushed
the
sockopt-iosafety
branch
from
c0c44c7 to
e962079
Compare
asomers
force-pushed
the
sockopt-iosafety
branch
from
e962079 to
eb5cd51
Compare
asomers
force-pushed
the
sockopt-iosafety
branch
2 times, most recently
from
cbda372 to
2e0cf97
Compare
asomers
force-pushed
the
sockopt-iosafety
branch
from
2e0cf97 to
0ddf22d
Compare
* socket * socketpair * listen * setsockopt * getsockopt
asomers
force-pushed
the
sockopt-iosafety
branch
from
0ddf22d to
c1317e4
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.