Fix re-registration of internal events after fork #1599
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If adding an (internal) descriptor to epoll fails, mark it for not being re-registered after fork (this would throw an exception).
In my case, during
notify_fork()
the io_uring service (re)registers with the epoll reactor. As the eventfd descriptor is already registered,EPOLL_CTL_ADD
fails withEEXIST
(which is ignored here). During re-registration after fork, epoll (again) refuses the 2nd registration of the epoll descriptor and the child crashes because of an exception:Call stack during
fork_prepare
:Call stack during
fork_child
:Reproducer (should dump the output of the
top
command to a file):