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

Correct the names of shared region functions. #5585

Merged
merged 1 commit into from
Nov 27, 2024

Conversation

magnumripper
Copy link
Member

The type is region_t but the functions are init/alloc/free_region().

Closes #5571 but copies of the functions still remain in yescrypt directory, not sure if they are identical or not.

The type is region_t but the functions are init/alloc/free_region().

Closes openwall#5571 but copies of the functions still remain in yescrypt
directory, not sure if they are identical or not.
Copy link
Member

@solardiz solardiz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me.

The copies under yescrypt are all static, so should not clash with these at link time, and not at compile time either because yescrypt files do not inlcude our memory.*, and our formats that use yescrypt only include yescrypt.h and not any of the .c files from there.

@magnumripper magnumripper merged commit 7df682c into openwall:bleeding-jumbo Nov 27, 2024
35 of 36 checks passed
@magnumripper magnumripper deleted the region_t branch November 27, 2024 01:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Clean up the memory regions API
2 participants