Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

Sign up

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

rust-lang / rust Public

Notifications You must be signed in to change notification settings
Fork 13.3k
Star 103k

Code
Issues 5k+
Pull requests 716
Actions
Projects 9
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Projects
Security
Insights

Only use `clone3` when needed for pidfd#89930

Merged

bors merged 4 commits intorust-lang:masterrust-lang/rust:masterfrom

cuviper:avoid-clone3cuviper/rust:avoid-clone3Copy head branch name to clipboard

Nov 11, 2021

Conversation Commits4 (4)Checks Files changed

Commits

Commits on Nov 5, 2021

Only use `clone3` when needed for pidfd
cuviper
committed
Update another comment on fork vs. clone3
cuviper
committed
Also note tool expectations of fork vs clone3

cuviper
and
joshtriplett
committed
Revert "Do not call getpid wrapper after fork in tests"
cuviper
committed

Footer

© 2025 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.