From: "Theodore Ts'o" <tytso@mit.edu>
To: Kees Cook <keescook@chromium.org>
Cc: James Morris <jmorris@namei.org>,
linux-security-module@vger.kernel.org,
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 02:16:58 -0400 [thread overview]
Message-ID: <20140719061658.GK18775@thunk.org> (raw)
In-Reply-To: <20140718191908.GA20534@www.outflux.net>
On Fri, Jul 18, 2014 at 12:19:08PM -0700, Kees Cook wrote:
> Hi James,
>
> Please pull these seccomp changes for 3.17.
>
> (And if I should base off something other than security-next, please
> let me know. Or if there are any things I should be doing differently
> with this tree.)
One note; there is a (interim) syscall number collision with the new
getrandom(2) system call. I'm sure Linus will be able to handle it,
and fix it up, but I just wanted to give a heads up that depending on
which pull request hits mainline first, the syscall number for either
the new seccomp(2) or getrandom(2) may end up changing.
I've been warning people not to try to use getrandom(2) or check
anything into LibreSSL, et. al., until the patch is finalized and in
Linus's tree, but if you have userspace users already using the
syscall assignments in this patch series, please let me know and I can
try to make adjustments on my side.
Cheers,
- Ted
next prev parent reply other threads:[~2014-07-19 8:55 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 [this message]
2014-07-19 14:49 ` Kees Cook
2014-07-19 21:50 ` Theodore Ts'o
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=20140719061658.GK18775@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox