test/vdso-proxy: handle merged vma-s #2816
Conversation
There was a problem hiding this comment.
Pull Request Overview
This PR enhances the vdso-proxy test to handle the [vvar_vclock] virtual memory area and refactors the VMA comparison logic in the check_vvar_vdso function to properly handle overlapping and split memory regions.
- Added recognition of
[vvar_vclock]mappings as vvar/vdso regions - Rewrote the VMA comparison algorithm to handle VMA splits and partial overlaps more accurately
- Fixed the loop increment logic to properly advance through both before/after VMA arrays
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
avagin
force-pushed
the
vdso-merge-vmas
branch
from
0d8598d to
e70a912
Compare
There was a problem hiding this comment.
Pull Request Overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated 2 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
When we compare two list of vma-s, we need to take into account that some of them could be merged. Fixes #12286 Signed-off-by: Andrei Vagin <avagin@google.com>
avagin
force-pushed
the
vdso-merge-vmas
branch
from
e70a912 to
4315172
Compare
There was a problem hiding this comment.
Pull Request Overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
1 participant
When we compare two list of vma-s, we need to take into account that some of them could be merged.
Fixes #2817