From: Kees Cook <keescook@chromium.org>
To: James Morris <jmorris@namei.org>
Cc: linux-kernel@vger.kernel.org, "Mickaël Salaün" <mic@digikod.net>,
"Ricky Zhou" <rickyz@chromium.org>,
linux-security-module@vger.kernel.org
Subject: [GIT PULL] seccomp fixes for v4.9-rc4
Date: Tue, 1 Nov 2016 10:46:12 -0700 [thread overview]
Message-ID: <20161101174612.GA72520@beast> (raw)
Hi,
Please pull these seccomp fixes for v4.9-rc4.
Thanks!
-Kees
The following changes since commit 07d9a380680d1c0eb51ef87ff2eab5c994949e69:
Linux 4.9-rc2 (2016-10-23 17:10:14 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/seccomp-v4.9-rc4
for you to fetch changes up to d881d25cf5bc2fafbbfb383a475278977e1bd55a:
samples/seccomp: Support programs with >256 instructions (2016-11-01 08:58:17 -0700)
----------------------------------------------------------------
- fix function prototype documentation
- fix samples to include NNP setting
- fix samples to avoid rule truncation
- fix samples hostprogs variable in Makefile
----------------------------------------------------------------
Mickaël Salaün (1):
seccomp: Fix documentation
Ricky Zhou (3):
samples/seccomp: Fix hostprogs variable
samples/seccomp: Enable PR_SET_NO_NEW_PRIVS in dropper
samples/seccomp: Support programs with >256 instructions
kernel/seccomp.c | 7 +++----
samples/seccomp/Makefile | 4 ++--
samples/seccomp/bpf-helper.c | 38 +++++++++++++++++++-------------------
samples/seccomp/dropper.c | 7 +++++--
4 files changed, 29 insertions(+), 27 deletions(-)
--
Kees Cook
Nexus Security
next reply other threads:[~2016-11-01 17:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-01 17:46 Kees Cook [this message]
2016-11-01 22:43 ` [GIT PULL] seccomp fixes for v4.9-rc4 James Morris
2016-11-02 2:07 ` Kees Cook
2016-11-04 16:35 ` 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=20161101174612.GA72520@beast \
--to=keescook@chromium.org \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mic@digikod.net \
--cc=rickyz@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;
as well as URLs for NNTP newsgroup(s).