Skip to content

Use host's rng when communication is enabled #914

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

Merged
merged 3 commits into from
Aug 23, 2019
Merged

Use host's rng when communication is enabled #914

merged 3 commits into from
Aug 23, 2019

Conversation

pvdrz
Copy link
Contributor

@pvdrz pvdrz commented Aug 19, 2019

This uses the host's randomness when the communication enabled flag is used. I am not sure about the error handling. I was thinking about fallbacking to rand if getrandom fails and also print something so the user knows miri is not using the host's rng because it failed. Let me know what you think.

Related issue: #800.

r? @RalfJung @oli-obk

@oli-obk
Copy link
Contributor

oli-obk commented Aug 20, 2019

@bors r+ lgtm then

@bors
Copy link
Contributor

bors commented Aug 20, 2019

📌 Commit b44fd97 has been approved by oli-obk

bors added a commit that referenced this pull request Aug 20, 2019
Use host's rng when communication is enabled

This uses the host's randomness when the communication enabled flag is used. I am not sure about the error handling. I was thinking about fallbacking to `rand` if `getrandom` fails and also print something so the user knows miri is not using the host's rng because it failed. Let me know what you think.

Related issue: #800.

r? @RalfJung @oli-obk
@bors
Copy link
Contributor

bors commented Aug 20, 2019

⌛ Testing commit b44fd97 with merge 07985a3...

@RalfJung
Copy link
Member

Also could you expand the -Zmiri-enable-communication docs to mention this? (Can be in a separate PR.)

@pvdrz
Copy link
Contributor Author

pvdrz commented Aug 20, 2019

Also could you expand the -Zmiri-enable-communication docs to mention this? (Can be in a separate PR.)

Sure

@RalfJung
Copy link
Member

@bors r- retry

@RalfJung
Copy link
Member

Thanks!

@bors r+

@bors
Copy link
Contributor

bors commented Aug 23, 2019

📌 Commit f53b5b0 has been approved by RalfJung

@bors
Copy link
Contributor

bors commented Aug 23, 2019

⌛ Testing commit f53b5b0 with merge 631d5fa...

bors added a commit that referenced this pull request Aug 23, 2019
Use host's rng when communication is enabled

This uses the host's randomness when the communication enabled flag is used. I am not sure about the error handling. I was thinking about fallbacking to `rand` if `getrandom` fails and also print something so the user knows miri is not using the host's rng because it failed. Let me know what you think.

Related issue: #800.

r? @RalfJung @oli-obk
@bors
Copy link
Contributor

bors commented Aug 23, 2019

☀️ Test successful - checks-travis, status-appveyor
Approved by: RalfJung
Pushing 631d5fa to master...

@bors bors merged commit f53b5b0 into rust-lang:master Aug 23, 2019
@pvdrz pvdrz deleted the use-host-rng branch August 23, 2019 15:29
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.

4 participants