Skip to content

Add function getpeereid for AIX #4524

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 1 commit into from
Jul 3, 2025
Merged

Conversation

xingxue-ibm
Copy link
Contributor

Description

AIX provides getpeereid in libc even though it is not mandated by POSIX. Since the tokio crate has a dependency on this function, this PR makes it available in the libc crate.

Sources

Checklist

  • Relevant tests in libc-test/semver have been updated
  • No placeholder or unstable values like *LAST or *MAX are
    included (see #3131)
  • Tested locally (cd libc-test && cargo test --target mytarget);
    especially relevant for platforms that may not be checked in CI

@tgross35 tgross35 added this pull request to the merge queue Jul 3, 2025
@collinfunk
Copy link
Contributor

collinfunk commented Jul 3, 2025

Can also confirm this is the case without logging into AIX. The getpeereid function declaration is hidden in a way that has caused me problems a few times previously. :)

@collinfunk
Copy link
Contributor

@tgross35 Shouldn't it be merged to libc-0.2, though?

@tgross35
Copy link
Contributor

tgross35 commented Jul 3, 2025

Everything goes through main, just add the label if you'd like me to pick something up for 0.2 (which should be pretty much everything):

@rustbot label +stable-nominated

@rustbot rustbot added the stable-nominated This PR should be considered for cherry-pick to libc's stable release branch label Jul 3, 2025
@xingxue-ibm
Copy link
Contributor Author

Thank you so much!

@collinfunk
Copy link
Contributor

Everything goes through main, just add the label if you'd like me to pick something up for 0.2 (which should be pretty much everything)

Yep, I figured I could add it myself. But wasn't sure if it was correct to do so.

Thank you for the clarification!

@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jul 3, 2025
@tgross35 tgross35 added this pull request to the merge queue Jul 3, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jul 3, 2025
@tgross35 tgross35 added this pull request to the merge queue Jul 3, 2025
Merged via the queue into rust-lang:main with commit 8e6f36c Jul 3, 2025
48 of 51 checks passed
tgross35 pushed a commit to tgross35/rust-libc that referenced this pull request Jul 29, 2025
(backport <rust-lang#4524>)
(cherry picked from commit 336e3f1)
@tgross35 tgross35 mentioned this pull request Jul 29, 2025
github-merge-queue bot pushed a commit that referenced this pull request Jul 29, 2025
(backport <#4524>)
(cherry picked from commit 336e3f1)
@tgross35 tgross35 added stable-applied This PR has been cherry-picked to libc's stable release branch and removed stable-nominated This PR should be considered for cherry-pick to libc's stable release branch labels Jul 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
O-unix stable-applied This PR has been cherry-picked to libc's stable release branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants