Am I missing where this article actually proposes this “isolated execution environment”? It’s mentioned in the intro and summary (and title), but the rest of the post is mainly a list of why it’s hard to do early verification of eBPF code.<p>Okay, this is true!<p>So I’m left wanting to know why the author thinks less rigid “isolation” is a suitable answer to the problem. “JavaScript does something similar” is the only detail I could find. But JavaScript notably does not run in the kernel.<p>Ultimately this just seems like a post saying “it’s too hard to do everything we want within the current limitations of eBPF. But makes no effort to explain why getting rid of these strictures would be worth the huge security and reliability hole it would be creating, or how they would avoid those issues.