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.

Sign up for GitHub

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

Jump to bottom

Only use clone3 when needed for pidfd #89924

Merged
merged 3 commits into from
Oct 16, 2021
Merged

Only use clone3 when needed for pidfd #89924

merged 3 commits into from
Oct 16, 2021

Commits on Oct 15, 2021

  1. Only use clone3 when needed for pidfd 

    In rust-lang#89522 we learned that `clone3` is interacting poorly with Gentoo's
`sandbox` tool. We only need that for the unstable pidfd extensions, so
otherwise avoid that and use a normal `fork`.
    @cuviper
    cuviper committed Oct 15, 2021
    Configuration menu
    Copy the full SHA
    de2e483 View commit details
    Browse the repository at this point in the history

  2. Update another comment on fork vs. clone3

    @cuviper
    cuviper committed Oct 15, 2021
    Configuration menu
    Copy the full SHA
    ad6e5e1 View commit details
    Browse the repository at this point in the history

  3. Also note tool expectations of fork vs clone3 

    Co-authored-by: Josh Triplett <josh@joshtriplett.org>
    @cuviper @joshtriplett
    cuviper and joshtriplett authored Oct 15, 2021
    Configuration menu
    Copy the full SHA
    74ef530 View commit details
    Browse the repository at this point in the history