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>,
Kees Cook <keescook@chromium.org>,
Oleg Nesterov <oleg@redhat.com>,
Pranith Kumar <bobby.prani@gmail.com>,
Tycho Andersen <tycho.andersen@canonical.com>
Subject: [PULL] seccomp update (next)
Date: Wed, 15 Jul 2015 11:56:24 -0700 [thread overview]
Message-ID: <20150715185624.GA22223@www.outflux.net> (raw)
Hi,
Please pull these seccomp changes for next.
Thanks!
-Kees
The following changes since commit b3bddffd35a0b77eee89760eb94cafa18dc431f5:
Merge branch 'next' of git://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity into next (2015-06-18 23:28:40 +1000)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/seccomp-next
for you to fetch changes up to 221272f97ca528048a577a3ff23d7774286ca5fd:
seccomp: swap hard-coded zeros to defined name (2015-07-15 11:52:54 -0700)
----------------------------------------------------------------
Various updates and cleanups for seccomp
----------------------------------------------------------------
Kees Cook (1):
seccomp: swap hard-coded zeros to defined name
Pranith Kumar (1):
seccomp: Replace smp_read_barrier_depends() with lockless_dereference()
Tycho Andersen (1):
seccomp: add ptrace options for suspend/resume
include/linux/ptrace.h | 1 +
include/linux/seccomp.h | 2 +-
include/uapi/linux/ptrace.h | 6 ++++--
kernel/ptrace.c | 13 +++++++++++++
kernel/seccomp.c | 17 ++++++++++++-----
5 files changed, 31 insertions(+), 8 deletions(-)
--
Kees Cook
Chrome OS Security
next reply other threads:[~2015-07-15 18:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 18:56 Kees Cook [this message]
2015-07-20 6:58 ` James Morris
-- strict thread matches above, loose matches on Subject: below --
2016-07-07 17:59 Kees Cook
2016-07-07 23:47 ` James Morris
2016-06-14 17:57 Kees Cook
2016-06-17 7:15 ` James Morris
2016-06-17 18:55 ` Andy Lutomirski
2016-06-18 7:02 ` Kees Cook
2016-06-18 10:21 ` Andy Lutomirski
2016-06-19 22:45 ` Andy Lutomirski
2016-01-05 23:40 Kees Cook
2014-11-25 19:43 Kees Cook
2014-11-26 13:23 ` James Morris
2014-11-26 21:46 ` Stephen Rothwell
2014-11-26 21:59 ` Kees Cook
2014-11-27 23:37 ` James Morris
2014-12-01 20:34 ` Kees Cook
2014-12-01 22:56 ` James Morris
2014-12-01 23:06 ` Kees Cook
2014-12-02 7:56 ` 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=20150715185624.GA22223@www.outflux.net \
--to=keescook@chromium.org \
--cc=bobby.prani@gmail.com \
--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=tycho.andersen@canonical.com \
/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®