Skip to content

Conversation

igchor
Copy link
Member

@igchor igchor commented Mar 12, 2024

Whenever allocation larger than the largest allocation class was requested base_alloc_global was calling ba_os_alloc and wasn't marking the memory in any way. This was problematic as address returned from ba_os_alloc could have been the same as an address used for other instance of umf_ba_pool_t. If that other instance had been destroyed the memory address would still be marked as inaccessible.

This fixes build on: #88

@igchor igchor requested a review from a team as a code owner March 12, 2024 19:29
Whenever allocation larger than the largest allocation class
was requested base_alloc_global was calling ba_os_alloc and
wasn't marking the memory in any way. This was problematic as
address returned from ba_os_alloc could have been the same as
an address used for other instance of umf_ba_pool_t. If that
other instance had been destroyed the memory address would
still be marked as inaccessible.
@bratpiorka bratpiorka merged commit 3f67e0e into oneapi-src:main Mar 13, 2024
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.

3 participants