fix mempool bug,when use MM_BACKTRACE #8511
Merged
Conversation
This file contains 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
anjiahao1
force-pushed
the
mempool_bug
branch
2 times, most recently
from
a3f844e
to
7ecd392
Compare
xiaoxiang781216
approved these changes
Feb 12, 2023
pkarashchenko
approved these changes
Feb 12, 2023
caculate blk address when mempool_multiple_free have a bug. need a real blocksize to caulate the memory address. Signed-off-by: anjiahao <anjiahao@xiaomi.com>
Signed-off-by: anjiahao <anjiahao@xiaomi.com>
anjiahao1
force-pushed
the
mempool_bug
branch
from
7ecd392
to
4fdbc16
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
fix mempool bug,when use MM_BACKTRACE
Impact
mempool
Testing
Vela
bug 1: Use
MM_BACLTRACE, calculated memory return address error.bug 2:
alistis not protected when traversing