On: Lucet: Native WebAssembly Compiler and Runtime

[kllrnohj]

It also compromises on resource abuse: "lucet does not currently provide a framework for protecting against guests that consume excessive CPU time (e.g. via an infinite loop). These protections must be provided by the host environment."

I'm not sure how you're supposed to handle that, either, given host environment usually does limiting at a process granularity but this doesn't use multiple processes.

[int_19h → kllrnohj]

Most OSes have a way to specify priority for a given thread.

[kllrnohj → int_19h]

Priority yes, but that's barely useful. cgroups, rlimits, cpulimit, etc... are far more useful here, and are all per-process.

[kentonv → kllrnohj]

You can use timer_create to arrange to deliver a signal after some amount of CPU time elapsed, then terminate the sandbox from the signal handler.