Re: [RFC PATCH 0/3] Introduce a classic BPF filter cache for seccomp
From: Alexei Starovoitov
Date: Fri Nov 20 2026 - 14:37:41 EST
On Thu, Nov 19, 2026 at 10:48 PM Xu Kuohai <xukuohai@xxxxxxxxxxxxxxx> wrote:
> The kernel repeatedly translates and JIT-compiles these same cBPF
> programs, wasting CPU cycles and slowing down bulk startup of
> identically sandboxed workloads. cBPF lacks dynamic instruction patching
There is no VM startup number in the series
which makes me question the whole thing.
> features like tail calls or tracing. Its JITed instructions remain
> immutable at runtime. This makes it possible to share the same cBPF
> filter between different processes.
Immutable is not enough. The image depends on the caps of the task
that loads the filter.
Also any task can time seccomp() and learn that somebody has this filter.
seccomp_get_filter() needs CAP_SYS_ADMIN for that today.
fork() shares the filter already, see copy_seccomp().
A launcher can install the common filter once and fork the VMs.
I don't think we need this.
pw-bot: cr