Skip to content
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

Enable Umbra to proactively track memory allocation #1798

Open
zhaoqin opened this issue Oct 22, 2015 · 2 comments
Open

Enable Umbra to proactively track memory allocation #1798

zhaoqin opened this issue Oct 22, 2015 · 2 comments

Comments

@zhaoqin
Copy link
Contributor

zhaoqin commented Oct 22, 2015

Umbra is the module to maintain the shadow memory mapping for application memory. Currently, Umbra does not track the memory allocation but wait for the client calling shadow memory creation routines to create shadow memory. Umbra should be able to proactively track the allocation and manage the shadow memory accordingly. The challenges to the proactively tracking is that there are not only mmap and NtAllocateVirtualMemory that allocates memory from the OS, there are other system calls.
One option is to use DrMalloc (xref #824).

@derekbruening
Copy link
Contributor

We also want to prevent a tool's mappings from conflicting. We want to put Umbra logic at 3 control points: DR placement (on Linux at least, by default today we can reload DR at inject time), priv lib placement, and app mmap placement.

@derekbruening
Copy link
Contributor

We were hoping that this could help ensure umbra's assumption of nothing being mapped in the 0x7fff'ff4-0x7fff'ff8 gap.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants