Right now, our seccomp rule specifications have this strange behaviour where if two arguments touch the same argument index, the argument list is treated as a series of OR conditions rather than AND conditions. This was added by e9193ba to fix a breaking change, but the net result is that our seccomp rule generation feels at least slightly unpredictable as a result.

We should really rework this alongside the longer-term fix for #2151.