-
Notifications
You must be signed in to change notification settings - Fork 406
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Prevent memory coalescing memory if cap-bounds do not span full length
During a GC sweep, coalescing contiguous memory that spans two separate system OS allocations (e.g. using mmap()), causes memory leakage in CHERI systems. This is because the capability used to represent such coalesced (expanded) memory regions has memory bounds derived from the original allocation syscall (smaller than the size of the coalesced memory). To prevent a client being given a capability with invalid bounds, such coalescing is prevented. 1. Add hblk pointer within header during re-allocation of GC'd memory. 2. Prevent coalescing in either directions when capability bounds do not span the size of the coalesced memory. 3. Derive only valid pointers when coalescing memory
- Loading branch information
Dejice Jacob
committed
Nov 11, 2021
1 parent
9009e65
commit d8ecfa3
Showing
2 changed files
with
20 additions
and
1 deletion.
There are no files selected for viewing
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
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