Skip to content

musl: rename __ipc_perm_key #4437

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

xbjfk
Copy link
Contributor

@xbjfk xbjfk commented May 1, 2025

Description

This change renames the internal name __ipc_perm_key to __key in the ipc_perm struct for musl libc, to be consistent with the __seq field as well as the glibc version of the same type. This works, because __ipc_perm_key is defined as __key, effectively adding an alias to the field. __seq is defined in the same way, as an alias to __ipc_perm_seq, however unlike __key this internal name was not present in the first commit __seq

Sources

musl: __key define/alias
musl: ipc_perm type
glibc version of ipc_perm in libc crate
code search for __ipc_perm_key (only auto generated code and musl mirrors)

Checklist

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

no-one uses __ipc_perm_key as this is a musl implementation detail musl
defines `__key` as an alias to this field. `key` is also defined as an
alias when _GNU_SOURCE or _BSD_SOURCE is defined, however `__key` is
chosen for compatibility with the glibc version.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants