From: Kees Cook <keescook@chromium.org>
To: James Morris <james.l.morris@oracle.com>
Cc: linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org,
Tycho Andersen <tycho@docker.com>
Subject: [GIT PULL] seccomp updates for next
Date: Tue, 28 Nov 2017 16:38:19 -0800 [thread overview]
Message-ID: <20171129003819.GA30686@beast> (raw)
Hi James,
Please pull these seccomp changes for next. This implements an interface
for examining seccomp filter metadata when using CRIU.
Thanks!
-Kees
The following changes since commit 4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323:
Linux 4.15-rc1 (2017-11-26 16:01:47 -0800)
are available in the git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/seccomp-next
for you to fetch changes up to 26500475ac1b499d8636ff281311d633909f5d20:
ptrace, seccomp: add support for retrieving seccomp metadata (2017-11-28 15:41:01 -0800)
----------------------------------------------------------------
add support for retrieving seccomp filter metadata (Tycho Andersen)
----------------------------------------------------------------
Tycho Andersen (2):
seccomp: hoist out filter resolving logic
ptrace, seccomp: add support for retrieving seccomp metadata
include/linux/seccomp.h | 8 ++++
include/uapi/linux/ptrace.h | 6 +++
kernel/ptrace.c | 4 ++
kernel/seccomp.c | 106 +++++++++++++++++++++++++++++++-------------
4 files changed, 94 insertions(+), 30 deletions(-)
--
Kees Cook
Pixel Security
next reply other threads:[~2017-11-29 0:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 0:38 Kees Cook [this message]
2017-11-29 1:55 ` [GIT PULL] seccomp updates for next James Morris
-- strict thread matches above, loose matches on Subject: below --
2018-12-12 23:16 Kees Cook
2018-12-13 0:08 ` James Morris
2017-08-15 22:03 Kees Cook
2017-08-16 2:33 ` James Morris
2017-06-26 17:02 Kees Cook
2017-06-27 3:27 ` 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=20171129003819.GA30686@beast \
--to=keescook@chromium.org \
--cc=james.l.morris@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=tycho@docker.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