From: "Theodore Ts'o" <tytso@mit.edu>
To: Kees Cook <keescook@chromium.org>
Cc: James Morris <jmorris@namei.org>,
linux-security-module <linux-security-module@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Andy Lutomirski <luto@amacapital.net>,
Oleg Nesterov <oleg@redhat.com>, Will Drewry <wad@chromium.org>,
Julien Tinnes <jln@chromium.org>,
David Drysdale <drysdale@google.com>
Subject: Re: [PULL] seccomp update (3.17)
Date: Sat, 19 Jul 2014 17:50:55 -0400 [thread overview]
Message-ID: <20140719215055.GA5017@thunk.org> (raw)
In-Reply-To: <CAGXu5jLjhXz3G-R18a=4U4OqSo8hLdW7OocCcLaEBLfYs=mAtA@mail.gmail.com>
On Sat, Jul 19, 2014 at 07:49:55AM -0700, Kees Cook wrote:
>
> No worries -- the only user of the seccomp syscall that I know of is
> the seccomp regression testing suite, and that'd be trivially to fix.
>
> I would note that the seccomp series includes adding the syscall also
> to ARM and MIPS, so from a collision fixing perspective, it may be
> fewer edits to fix getrandom instead. :)
I've only wired up x86 and x86_64 for getrandom(2) so far. I had
assumed the ARM and MIPS folks would prefer to wire up new syscalls on
their own...
- Ted
next prev parent reply other threads:[~2014-07-19 21:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 19:19 [PULL] seccomp update (3.17) Kees Cook
2014-07-19 6:16 ` Theodore Ts'o
2014-07-19 14:49 ` Kees Cook
2014-07-19 21:50 ` Theodore Ts'o [this message]
2014-07-19 7:36 ` James Morris
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=20140719215055.GA5017@thunk.org \
--to=tytso@mit.edu \
--cc=drysdale@google.com \
--cc=jln@chromium.org \
--cc=jmorris@namei.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=oleg@redhat.com \
--cc=wad@chromium.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.