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.

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

Rename malloc_revoke() to reduce reader confusion #2302

Open
rwatson opened this issue Jan 26, 2025 · 1 comment
Open

Rename malloc_revoke() to reduce reader confusion #2302

rwatson opened this issue Jan 26, 2025 · 1 comment
Labels
temporal Issues related to the temporal safety implementation(s)

Comments

@rwatson
Copy link
Member

rwatson commented Jan 26, 2025

The API name malloc_revoke(3) is causing confusion; it might be more clear to rename it to malloc_quarantine_drain() or malloc_revoke_barrier() or such. Suggestions welcome, but would be good to fix before 25.02. We should retain support for the old symbol, and possibly API, due to use in existing tutorials / etc, but prefer the new name in all writing.

@rwatson rwatson added the temporal Issues related to the temporal safety implementation(s) label Jan 26, 2025
@brooksdavis
Copy link
Member

How much compatibility do we want? Not breaking source or not breaking binaries?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
temporal Issues related to the temporal safety implementation(s)
Projects
None yet
Development

No branches or pull requests

2 participants