-
Notifications
You must be signed in to change notification settings - Fork 666
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
Remove return value from pause
#829
Conversation
Closes issue #827.
I'll redo this as #828, since it might create another conflict when adding to the changelog. |
@@ -12,7 +12,7 @@ fn test_wait_signal() { | |||
|
|||
// Safe: The child only calls `pause` and/or `_exit`, which are async-signal-safe. | |||
match fork().expect("Error: Fork Failed") { | |||
Child => pause().unwrap_or_else(|_| unsafe { _exit(123) }), | |||
Child => pause(), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe that you have to call _exit()
instead of letting the thread naturally exit because of how Rust's standard cleanup isn't signal safe or something. @asomers Can you verify this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep. The standard cleanup may try to access shared resources that were exclusively held by other threads at the time that fork
happened. But those other threads don't exist in the child, so your thread will never get the resources, and deadlock will result. That's why we call _exit
in child threads.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe I'm misunderstanding something but, isn't unwrap_or_else
only called if pause
fails and returns an error. Since that can't happend anymore _exit
can never be called, and would have never be called even without the change.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've fixed this in #836, for some reason this pull request is now "from unknown repository". I don't know how to fix that, so instead I created an new pr.
Closes issue #827.