On 10/3/23 10:38, Hengqi Chen wrote:
This patchset introduces two new operations which essentially
splits the SECCOMP_SET_MODE_FILTER process into two steps:
SECCOMP_LOAD_FILTER and SECCOMP_ATTACH_FILTER.
The SECCOMP_LOAD_FILTER loads the filter and returns a fd
which can be pinned to bpffs. This extends the lifetime of the
filter and thus can be reused by different processes.
A quick question to see if handling something else too is
possible/reasonable to do here too.
Let me explain our use case first.
For us (Alban in cc) it would be great if we can extend the lifetime of
the fd returned, so the process managing a seccomp notification in
userspace can easly crash or be updated. Today, if the agent that got
the fd crashes, all the "notify-syscalls" return ENOSYS in the target
process.
Our use case is we created a seccomp agent to use in Kubernetes
(github.com/kinvolk/seccompagent) and we need to handle either the agent
crashing or upgrading it. We were thinking tricks to have another
container that just stores fds and make sure that never crashes, but it
is not ideal (we checked tricks to use systemd to store our fds, but it
is not simpler either to use from containers).
If the agent crashes today, all the syscalls return ENOSYS. It will be
great if we can make the process doing the syscall just wait until a new
process to handle the notifications is up and the syscalls done in the
meantime are just queued. A mode of saying "if the agent crashes, just
queue notifications, one agent to pick them up will come back soon" (we
can of course limit reasonably the notification queue).
It seems the split here would not just work for that use case. I think
we would need to pin the attachment.
Do you think handling that is something reasonable to do in this series too?
I'll be afk until end next week. I'll catch up as soon as I'm back with
internet :)
Best,
Rodrigo
