From: Kees Cook <keescook@chromium.org>
To: James Morris <jmorris@namei.org>
Cc: 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: [PULL] seccomp update (3.17)
Date: Fri, 18 Jul 2014 12:19:08 -0700 [thread overview]
Message-ID: <20140718191908.GA20534@www.outflux.net> (raw)
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.)
Thanks!
-Kees
The following changes since commit 32c2e6752ff0f48fe03b9e1c7c64bde580a840d2:
ima: provide double buffering for hash calculation (2014-07-17 09:35:11 -0400)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/seccomp-3.17
for you to fetch changes up to c2e1f2e30daa551db3c670c0ccfeab20a540b9e1:
seccomp: implement SECCOMP_FILTER_FLAG_TSYNC (2014-07-18 12:13:40 -0700)
----------------------------------------------------------------
seccomp TSYNC support for 3.17
----------------------------------------------------------------
Kees Cook (12):
MAINTAINERS: create seccomp entry
seccomp: create internal mode-setting function
seccomp: extract check/assign mode helpers
seccomp: split mode setting routines
seccomp: add "seccomp" syscall
ARM: add seccomp syscall
MIPS: add seccomp syscall
sched: move no_new_privs into new atomic flags
seccomp: split filter prep from check and apply
seccomp: introduce writer locking
seccomp: allow mode setting across threads
seccomp: implement SECCOMP_FILTER_FLAG_TSYNC
MAINTAINERS | 10 +
arch/Kconfig | 1 +
arch/arm/include/uapi/asm/unistd.h | 1 +
arch/arm/kernel/calls.S | 1 +
arch/mips/include/uapi/asm/unistd.h | 15 +-
arch/mips/kernel/scall32-o32.S | 1 +
arch/mips/kernel/scall64-64.S | 1 +
arch/mips/kernel/scall64-n32.S | 1 +
arch/mips/kernel/scall64-o32.S | 1 +
arch/x86/syscalls/syscall_32.tbl | 1 +
arch/x86/syscalls/syscall_64.tbl | 1 +
fs/exec.c | 6 +-
include/linux/sched.h | 18 +-
include/linux/seccomp.h | 8 +-
include/linux/syscalls.h | 2 +
include/uapi/asm-generic/unistd.h | 4 +-
include/uapi/linux/seccomp.h | 7 +
kernel/fork.c | 49 ++++-
kernel/seccomp.c | 412 ++++++++++++++++++++++++++++++-----
kernel/sys.c | 4 +-
kernel/sys_ni.c | 3 +
security/apparmor/domain.c | 4 +-
22 files changed, 471 insertions(+), 80 deletions(-)
--
Kees Cook
Chrome OS Security
next reply other threads:[~2014-07-18 19:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 19:19 Kees Cook [this message]
2014-07-19 6:16 ` Theodore Ts'o
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=20140718191908.GA20534@www.outflux.net \
--to=keescook@chromium.org \
--cc=drysdale@google.com \
--cc=jln@chromium.org \
--cc=jmorris@namei.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
all inboxes | Powered by JetHome®