feat(bql): Ensure BQL is held during after_machine_init - #14
Open
lacraig2 wants to merge 1 commit into
Open
Conversation
This commit wraps the call to panda_callbacks_after_machine_init in panda_init with bql_lock() and bql_unlock(). This is critical to ensure that plugins (like the new native mmap manager) can safely perform Memory API operations during this callback without triggering bql_locked() assertion failures.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This commit wraps the call to panda_callbacks_after_machine_init in panda_init with bql_lock() and bql_unlock().
This is critical to ensure that plugins (like the new native mmap manager) can safely perform Memory API operations during this callback without triggering bql_locked() assertion failures.