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

Merge branch 'master' into 0.2 #130

Merged
merged 8 commits into from
Jan 9, 2020
Merged

Merge branch 'master' into 0.2 #130

merged 8 commits into from
Jan 9, 2020

Conversation

josephlr
Copy link
Member

@josephlr josephlr commented Jan 8, 2020

Similar to #116, we want to get #118 #126 #129 #125 and #128 into the 0.2 branch.

I didn't run into any notable merge conflicts.

newpavlov and others added 8 commits October 25, 2019 12:25
Signed-off-by: Joe Richey <joerichey@google.com>
Don't spin when polling /dev/random. We also remove the use of spin
locks when opening the persistent fd for platforms that require it.

For both these cases, we can just use the pthread lock/unlock methods
in libc. This includes adding Mutex and DropGuard abstractions.

Signed-off-by: Joe Richey <joerichey@google.com>
We no longer use spin-locks anywhere in getrandom, so remove any
interfaces which spin.

Signed-off-by: Joe Richey <joerichey@google.com>
Signed-off-by: Joe Richey <joerichey@google.com>
@josephlr josephlr changed the base branch from master to 0.2 January 8, 2020 19:17
@josephlr josephlr merged commit 0f14f2a into rust-random:0.2 Jan 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants