From: Kees Cook <keescook@chromium.org>
To: James Morris <james.l.morris@oracle.com>
Cc: linux-kernel@vger.kernel.org,
"Dmitry V. Levin" <ldv@altlinux.org>,
Eugene Syromiatnikov <esyr@redhat.com>,
Tycho Andersen <tycho@tycho.ws>
Subject: [GIT PULL] seccomp updates for v4.16-rc3
Date: Wed, 21 Feb 2018 17:04:11 -0800 [thread overview]
Message-ID: <20180222010411.GA34870@beast> (raw)
Hi James,
Please pull these seccomp changes for v4.16-rc3. These are fixes for the
get_metadata interface that landed during -rc1. While the new selftest
is strictly not a bug fix, I think it's in the same spirit of avoiding
bugs.
Thanks!
-Kees
The following changes since commit 26500475ac1b499d8636ff281311d633909f5d20:
ptrace, seccomp: add support for retrieving seccomp metadata (2017-11-28 15:41:01 -0800)
are available in the git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/seccomp-v4.16-rc3
for you to fetch changes up to d057dc4e35e16050befa3dda943876dab39cbf80:
seccomp: add a selftest for get_metadata (2018-02-21 16:56:03 -0800)
----------------------------------------------------------------
- Fix seccomp GET_METADATA to deal with fields sizes correctly (Tycho Andersen)
- Add selftest to make sure GET_METADATA doesn't regress (Tycho Andersen)
----------------------------------------------------------------
Tycho Andersen (3):
seccomp, ptrace: switch get_metadata types to arch independent
ptrace, seccomp: tweak get_metadata behavior slightly
seccomp: add a selftest for get_metadata
include/uapi/linux/ptrace.h | 4 +-
kernel/seccomp.c | 6 ++-
tools/testing/selftests/seccomp/seccomp_bpf.c | 61 +++++++++++++++++++++++++++
3 files changed, 67 insertions(+), 4 deletions(-)
--
Kees Cook
Pixel Security
next reply other threads:[~2018-02-22 1:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 1:04 Kees Cook [this message]
2018-02-22 18:52 ` [GIT PULL] seccomp updates for v4.16-rc3 James Morris
-- strict thread matches above, loose matches on Subject: below --
2018-02-22 1:11 Kees Cook
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=20180222010411.GA34870@beast \
--to=keescook@chromium.org \
--cc=esyr@redhat.com \
--cc=james.l.morris@oracle.com \
--cc=ldv@altlinux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tycho@tycho.ws \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.