From: Andy Lutomirski <luto@amacapital.net>
To: Kees Cook <keescook@chromium.org>
Cc: Christian Brauner <christian.brauner@ubuntu.com>,
Tycho Andersen <tycho@tycho.ws>,
Sargun Dhillon <sargun@sargun.me>,
Matt Denton <mpdenton@google.com>,
Chris Palmer <palmer@google.com>,
Jeffrey Vander Stoep <jeffv@google.com>,
Linux Containers <containers@lists.linux-foundation.org>,
Linux API <linux-api@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: seccomp feature development
Date: Mon, 18 May 2020 15:55:06 -0700 [thread overview]
Message-ID: <CALCETrXv82qFRRXvH0ELQScRkKFzp+ND_8pahD+YJ=0OWY8YWg@mail.gmail.com> (raw)
In-Reply-To: <202005181120.971232B7B@keescook>
On Mon, May 18, 2020 at 2:05 PM Kees Cook <keescook@chromium.org> wrote:
>
> Hi!
>
This is minor, but, if we grow seccomp_data, I would like to add the
other 32 bits of the syscall nr to it. Syscall numbers are unsigned
long, but they get munged into u32 for seccomp_data.
Sure, no one uses those high bits yet, but if we're extending things
anyway, let's support them.
next prev parent reply other threads:[~2020-05-18 22:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 21:04 seccomp feature development Kees Cook
2020-05-18 22:39 ` Jann Horn
2020-05-19 2:48 ` Aleksa Sarai
2020-05-19 10:35 ` Christian Brauner
2020-05-19 16:18 ` Alexei Starovoitov
2020-05-19 21:40 ` Kees Cook
2020-05-20 1:20 ` Aleksa Sarai
2020-05-20 5:17 ` Alexei Starovoitov
2020-05-20 6:18 ` Aleksa Sarai
2020-05-19 7:24 ` Sargun Dhillon
2020-05-19 8:30 ` Christian Brauner
2020-06-03 19:09 ` Kees Cook
2020-05-18 22:55 ` Andy Lutomirski [this message]
2020-05-19 7:09 ` Aleksa Sarai
2020-05-19 11:01 ` Christian Brauner
2020-05-19 13:42 ` Aleksa Sarai
2020-05-19 13:53 ` Aleksa Sarai
2020-05-19 10:26 ` Christian Brauner
2020-05-20 8:23 ` Sargun Dhillon
2020-05-19 14:07 ` Tycho Andersen
2020-05-20 9:05 ` Sargun Dhillon
2020-05-22 20:09 ` Sargun Dhillon
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='CALCETrXv82qFRRXvH0ELQScRkKFzp+ND_8pahD+YJ=0OWY8YWg@mail.gmail.com' \
--to=luto@amacapital.net \
--cc=christian.brauner@ubuntu.com \
--cc=containers@lists.linux-foundation.org \
--cc=jeffv@google.com \
--cc=keescook@chromium.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpdenton@google.com \
--cc=palmer@google.com \
--cc=sargun@sargun.me \
--cc=tycho@tycho.ws \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).