Re:The Bytecode Alliance: Building a secure, composable futu...
by BubRoss on Tuesday November 12, 2019 @02:49PM
(#21517419)
Shared memory can certainly do this. Even separate processes can use shared memory to communicate lock free using atomics.
Other than that, I wonder if nested page tables that are normally used for virtualization can be used to separate address spaces within a process.
Re:The Bytecode Alliance: Building a secure, composable futu...
by azakai on Tuesday November 12, 2019 @01:20PM
(#21516530)
Interesting! Is that written up somewhere public?
Re:The Bytecode Alliance: Building a secure, composable futu...
by JoshTriplett on Tuesday November 12, 2019 @01:21PM
(#21516559)
Some of it; see https://hacks.mozilla.org/2019/08/webassembly-interface-type... for the starting point that this will be based on.
Re:The Bytecode Alliance: Building a secure, composable futu...
by azakai on Tuesday November 12, 2019 @01:38PM
(#21516728)
Oh, where? I don't think I see anything about controlled memory sharing there, but I guess I missed it. Which section is it in?
Re:The Bytecode Alliance: Building a secure, composable futu...
by JoshTriplett on Tuesday November 12, 2019 @01:47PM
(#21516835)
It isn't yet, that work is still in progress. WIT is just the starting point that this would be based on.
(Sorry for the lack of more concrete information, documentation is still in progress.)
We're working on that. We want to make it possible for modules to share memory in a controlled way, without giving access to their entire address space.