3 ms·
> quarantining allocations forever [..] is insufficient for production In most cases that's true, but not all. ARM MTE + quarantine has just 1-2% overhead as t
by azakai 4y ago
> quarantining allocations forever [..] is insufficient for production
In most cases that's true, but not all. ARM MTE + quarantine has just 1-2% overhead as tested on Chrome:
https://security.googleblog.com/2022/05/retrofitting-temporal-memory-safety-on-c.html https://security.googleblog.com/2022/05/retrofitting-tempora...
Perhaps we'll see such techniques used in newer languages like Zig.
(This doesn't detract from your main point, of course - yes, Zig is simpler because it has less safety.)
- pcwalton 4y agoThe approach described there is significantly different from Zig's approach, which doesn't use MTE and quarantines forever. Note that Chromium never seriously considered quarantining forever as Zig does because leaking every allocation less than 4kB unless all allocations in that page are freed is not production viable.
- azakai 4y agoTrue, but I don't think Zig is committed to that particular idea and nothing else. Yeah, quarantining forever is going to have much more memory overhead. It might be fine for some use cases, but not a browser or anything else complex + long-running, I agree.