This repository has been archived by the owner on Jan 28, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 884
Overlapping memslots can corrupt linked list #234
Comments
Any specific reason you are referencing commit c072ad9? |
Na,it's just that I have checked out this version and using it actively with my modifications, but there was no change in the way of the memslot implementation since then, so it shouldn't be a problem.
in memslot_process_end_diff_type is the reason for it,because it just replaces an item with a version that is self-referencing (see memslot_init) and the links aren't updated anywhere as far as I can see |
This should fix it:
|
leecher1337
added a commit
to leecher1337/haxm
that referenced
this issue
Aug 15, 2019
Great thanks for your trouble shoot! I have added a comment in #199 for your reference. |
Thanks for your quick response and commit in #237. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the Bug
When I try to add a memblock that ends at the exact beginning of the next memblock via HAX_VM_IOCTL_SET_RAM, there seems to be a condition where the new block is being left as referencing itself via flink and blink causing an infinite loop in the driver.
See logfile below for details
Summary:
Host Environment
To Reproduce
Connect memory pages in the layout described in the logfile.
Expected Behavior
No self-referencing pointer in the linked list.
Reproducibility
100%
Diagnostic Information
HAXM log:
The text was updated successfully, but these errors were encountered: