-
-
Notifications
You must be signed in to change notification settings - Fork 3.2k
Fix #12007 (partially): use RVec for RLog callbacks #25412
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
seifreed
wants to merge
1
commit into
radareorg:master
Choose a base branch
from
seifreed:codex/issue-12007-rlog-rvector
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This loop walks
rlog->cbswith a raw element pointer, but callbacks are allowed to callr_log_add_callback/r_log_del_callbackwhile handling a log message. With the newRVecbackend,push_backcanreallocat capacity boundaries (e.g. when growing from 8 to 9 callbacks), which invalidatesitermid-loop and can lead to use-after-free or corrupted iteration; removals can also shift elements and skip callbacks. A safer approach is to iterate by index over a captured length (or clone/snapshot the vector) before invoking user callbacks.Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe good to fix what this comment mentions. even if its stupid to add and dlete log callbacks in the event of a logcallback execution it can happen and cause ugly crashes. i can think of two solutions:
forbid that (easier, fster, more direct). just have a boolean inside rlog that tells addcallback and delcallback that we are iterating and we wont accept them to run, just return error if thats the case. this boolean can be set and unset before and after this R_VEC_FOREACH loop.
add a second list of callbacks that is not iterated from here, fill it when we call add/dell a callback and sync it in an atomic way if there's any call. this will add more runtime code weight. and make log more complicated. but the resulting implementation will be more flexible.
i vote for the 1st option. what do you think? is there any relevant situation that im missing to be able to do that?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree with option 1 to keep it simple and avoid extra runtime weight.
One detail: r_log_add_callback/r_log_del_callback currently return void, so we can’t return an error without API changes.
I propose to guard callback iteration with a boolean lock and make add/del no-op while iterating.
That prevents iterator invalidation/crashes with minimal complexity.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sounds good to me, lets do that