fluencelabs/musl
1
0
Fork 0
mirror of https://github.com/fluencelabs/musl synced 2025-07-31 22:31:58 +00:00
Code Issues Projects Releases Wiki Activity

Add note on heap sharing.

Browse Source
This commit is contained in:
JF Bastien
2016-02-01 08:04:53 -08:00
parent acc1d6453b
commit 0430d8d821
1 changed files with 8 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
README.md
View File

@@ -150,6 +150,14 @@ stacks. libc's `malloc` would then use this basic memory manager to implement
runtime memory management, the same would be true for stack positioning, thread runtime memory management, the same would be true for stack positioning, thread
stacks, and thread-local storage allocation. stacks, and thread-local storage allocation.
Interesting applications can be built when modules *don't* share the same
heap. They need to communicate through copy-in / copy-out functionality (such as
Linux' `copy_from_user` / `copy_to_user` functions), and are then entirely
isolated from each other except for their API boundary. This allows applications
to instantiate their heap in a private closure and only expose APIs, providing
good isolation properties and preventing user code from overflow and other
security issues.
## Why do dynamic linking now? ## Why do dynamic linking now?
These basic experiments are finding bugs in the toolchain, if anything they're These basic experiments are finding bugs in the toolchain, if anything they're