From: Kees Cook <keescook@chromium.org>
To: ksummit-discuss@lists.linuxfoundation.org
Subject: [Ksummit-discuss] [TECH TOPIC] seccomp feature development
Date: Wed, 20 May 2020 09:17:41 -0700 [thread overview]
Message-ID: <202005200917.71E6A5B20@keescook> (raw)
As recently outlined[1], there are are a number of seccomp topics that
need discussion:
- fd passing
- deep argument inspection
- changing structure sizes
- syscall bitmasks
Specifically, seccomp needs to grow the ability to inspect Extensible
Argument syscalls, which requires that it inspect userspace memory
without Time-of-Check/Time-of-Use races and without double-copying.
Additionally, since the structures can grow and be nested, there needs
to be a way to deal with flattening the arguments into a linear buffer
that can be examined by seccomp's BPF dialect. All of this also needs to
be handled by the USER_NOTIF implementation. Finally, fd passing needs
to be finished, and there needs to be an exploration of syscall bitmasks
to augment the existing filters to gain back some performance.
-Kees
(This has been submitted to the LPC site as well[2].)
[1] https://lore.kernel.org/lkml/202005181120.971232B7B@keescook/
[2] https://linuxplumbersconf.org/event/7/abstracts/596/
--
Kees Cook
_______________________________________________
Ksummit-discuss mailing list
Ksummit-discuss@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss
next reply other threads:[~2020-05-20 16:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 16:17 Kees Cook [this message]
2020-05-20 16:31 ` [Ksummit-discuss] [TECH TOPIC] seccomp feature development Al Viro
2020-05-20 18:05 ` Kees Cook
2020-05-20 18:16 ` Al Viro
2020-05-20 18:27 ` Linus Torvalds
2020-05-20 19:04 ` Kees Cook
2020-05-20 19:08 ` Linus Torvalds
2020-05-20 20:24 ` Christian Brauner
2020-05-20 20:52 ` Kees Cook
2020-05-20 21:02 ` Christian Brauner
2020-05-22 4:06 ` Aleksa Sarai
2020-05-22 7:35 ` Christian Brauner
2020-05-22 11:27 ` Christian Brauner
2020-05-20 22:12 ` Alexei Starovoitov
2020-05-20 22:12 ` Alexei Starovoitov
2020-05-20 23:39 ` Kees Cook
2020-05-20 23:39 ` Kees Cook
2020-05-21 0:43 ` Alexei Starovoitov
2020-05-21 0:43 ` Alexei Starovoitov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202005200917.71E6A5B20@keescook \
--to=keescook@chromium.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.