Skip to content
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

v1.19.1 #9747

Merged
merged 5 commits into from
Jan 22, 2024
Merged

v1.19.1 #9747

merged 5 commits into from
Jan 22, 2024

Conversation

j-xiong
Copy link
Contributor

@j-xiong j-xiong commented Jan 19, 2024

For CI only. Don't merge. Will be pushed directly.

j-xiong and others added 4 commits January 18, 2024 16:02
A follow-up to commit e5a70c2. There is another error path
that the lock need to be released.

Signed-off-by: Jianxin Xiong <[email protected]>
(cherry picked from commit 826cffb)
Signed-off-by: Franz Pöschel <[email protected]>
(cherry picked from commit 22c9d04)
All write accesses to `wait->signal` are protected by the lock. The read
access should be protected, too.

Signed-off-by: Jianxin Xiong <[email protected]>
(cherry picked from commit e16f28a)
Sock variable handle goes out of scope and leaks the handle.
This cleans it up properly.

Signed-off-by: Zach Dworkin <[email protected]>
(cherry picked from commit e6bc224)
Signed-off-by: Jianxin Xiong <[email protected]>
@j-xiong j-xiong merged commit f85be90 into ofiwg:v1.19.x Jan 22, 2024
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants