From: Kees Cook <keescook@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Kees Cook <keescook@chromium.org>,
Matthew Denton <mpdenton@google.com>,
Sven Schnelle <svens@linux.ibm.com>,
Tycho Andersen <tycho@tycho.ws>
Subject: [GIT PULL] seccomp updates for v5.7-rc1
Date: Sun, 29 Mar 2020 21:16:07 -0700 [thread overview]
Message-ID: <202003292114.2252CAEF7@keescook> (raw)
Hi Linus,
Please pull these couple of seccomp updates for v5.7-rc1. They're both
mostly bug fixes that I wanted to have sit in linux-next for a while.
That's done now, so here they are for v5.7.
Thanks!
-Kees
The following changes since commit 11a48a5a18c63fd7621bb050228cebf13566e4d8:
Linux 5.6-rc2 (2020-02-16 13:16:59 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/seccomp-v5.7-rc1
for you to fetch changes up to 3db81afd99494a33f1c3839103f0429c8f30cb9d:
seccomp: Add missing compat_ioctl for notify (2020-03-29 21:10:51 -0700)
----------------------------------------------------------------
updates for seccomp
- allow TSYNC and USER_NOTIF together (Tycho Andersen)
- Add missing compat_ioctl for notify (Sven Schnelle)
----------------------------------------------------------------
Sven Schnelle (1):
seccomp: Add missing compat_ioctl for notify
Tycho Andersen (1):
seccomp: allow TSYNC and USER_NOTIF together
include/linux/seccomp.h | 3 +-
include/uapi/linux/seccomp.h | 1 +
kernel/seccomp.c | 15 ++++--
tools/testing/selftests/seccomp/seccomp_bpf.c | 74 ++++++++++++++++++++++++++-
4 files changed, 87 insertions(+), 6 deletions(-)
--
Kees Cook
next reply other threads:[~2020-03-30 4:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-30 4:16 Kees Cook [this message]
2020-03-30 20:40 ` [GIT PULL] seccomp updates for v5.7-rc1 pr-tracker-bot
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=202003292114.2252CAEF7@keescook \
--to=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpdenton@google.com \
--cc=svens@linux.ibm.com \
--cc=torvalds@linux-foundation.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.