Skip to content
Open
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next Next commit
flush instruction cache after performing relocations
Flush instruction cache to avoid executing stale code after performing relocations.
According to MSDN: "Applications should call FlushInstructionCache if they generate or modify code in memory. The CPU cannot detect the change, and may execute the old code it cached.".
After performing relocation we have modified executable code, so if we don't flush the cache maybe the old code without relocation is executed instead. So far the code has woked without flushing instruction cache but it's better to be safe.

https://msdn.microsoft.com/en-us/library/windows/desktop/ms679350(v=vs.85).aspx
  • Loading branch information
hMihaiDavid authored Dec 31, 2016
commit be6568111d709ac1c64fb70aeecf1ffc4a217c9a
3 changes: 3 additions & 0 deletions MemoryModule.c
Original file line number Diff line number Diff line change
Expand Up @@ -645,6 +645,9 @@ HMEMORYMODULE MemoryLoadLibraryEx(const void *data, size_t size,
} else {
result->isRelocated = TRUE;
}

// flush instruction cache to avoid executing stale code after performing relocations
FlushInstructionCache((HANDLE)-1, NULL, 0);
Comment thread
hMihaiDavid marked this conversation as resolved.
Outdated

// load required dlls and adjust function table of imports
if (!BuildImportTable(result)) {
Expand Down