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

Fix a small number of invalid unsafe code [round 2] #33942

Merged
merged 2 commits into from
Nov 25, 2019
Merged

Fix a small number of invalid unsafe code [round 2] #33942

merged 2 commits into from
Nov 25, 2019

Conversation

vtjnash
Copy link
Member

@vtjnash vtjnash commented Nov 25, 2019

I'm not quite sure why these weren't caught in the original PR, but basically all the same as those.

fixes #33899

More cases similar to those identified in #23914
fix #33899
We were releasing this lock a bit too early, before we finished with using `buf`.
@vtjnash vtjnash added io Involving the I/O subsystem: libuv, read, write, etc. embarrassing-bugfix Whoops! backport 1.0 labels Nov 25, 2019
@yuyichao
Copy link
Contributor

I'm not quite sure why these weren't caught in the original PR,

Because I fixed them until I got tired?

@vtjnash
Copy link
Member Author

vtjnash commented Nov 25, 2019

Haha, I just don't think I realized that there was still more to investigate at the time.

@vtjnash vtjnash merged commit 31bf76f into master Nov 25, 2019
@vtjnash vtjnash deleted the jn/33899 branch November 25, 2019 22:55
This was referenced Nov 29, 2019
@KristofferC KristofferC added the bugfix This change fixes an existing bug label Dec 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bugfix This change fixes an existing bug embarrassing-bugfix Whoops! io Involving the I/O subsystem: libuv, read, write, etc.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Distributed IOError: write: bad address in system call argument (EFAULT)
3 participants