All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
	"Christian Brauner" <christian.brauner@ubuntu.com>,
	"Eric Paris" <eparis@redhat.com>, "Jann Horn" <jannh@google.com>,
	"John Paul Adrian Glaubitz" <glaubitz@physik.fu-berlin.de>,
	"Michael Ellerman" <mpe@ellerman.id.au>,
	"Mickaël Salaün" <mic@linux.microsoft.com>,
	"Oleg Nesterov" <oleg@redhat.com>,
	"Serge E. Hallyn" <serge@hallyn.com>,
	"Tyler Hicks" <tyhicks@linux.microsoft.com>,
	"Will Drewry" <wad@chromium.org>
Subject: [GIT PULL] seccomp fixes for v5.10-rc5
Date: Fri, 20 Nov 2020 11:13:51 -0800	[thread overview]
Message-ID: <202011201112.C7CFF68B07@keescook> (raw)

Hi Linus,

Please pull these seccomp fixes for v5.10-rc5. This gets the seccomp
selftests running against on powerpc and sh, and fixes an audit
reporting oversight noticed in both seccomp and ptrace.

Thanks!

-Kees

The following changes since commit 09162bc32c880a791c6c0668ce0745cf7958f576:

  Linux 5.10-rc4 (2020-11-15 16:44:31 -0800)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/seccomp-v5.10-rc5

for you to fetch changes up to 4c222f31fb1db4d590503a181a6268ced9252379:

  selftests/seccomp: sh: Fix register names (2020-11-20 11:03:08 -0800)

----------------------------------------------------------------
seccomp fixes for v5.10-rc5

- Fix typos in seccomp selftests on powerpc and sh (Kees Cook)

- Fix PF_SUPERPRIV audit marking in seccomp and ptrace (Mickaël Salaün)

----------------------------------------------------------------
Kees Cook (2):
      selftests/seccomp: powerpc: Fix typo in macro variable name
      selftests/seccomp: sh: Fix register names

Mickaël Salaün (2):
      ptrace: Set PF_SUPERPRIV when checking capability
      seccomp: Set PF_SUPERPRIV when checking capability

 kernel/ptrace.c                               | 16 +++++-----------
 kernel/seccomp.c                              |  5 ++---
 tools/testing/selftests/seccomp/seccomp_bpf.c |  8 ++++----
 3 files changed, 11 insertions(+), 18 deletions(-)

-- 
Kees Cook

             reply	other threads:[~2020-11-20 19:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-20 19:13 Kees Cook [this message]
2020-11-21 18:39 ` [GIT PULL] seccomp fixes for v5.10-rc5 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=202011201112.C7CFF68B07@keescook \
    --to=keescook@chromium.org \
    --cc=christian.brauner@ubuntu.com \
    --cc=eparis@redhat.com \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=jannh@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mic@linux.microsoft.com \
    --cc=mpe@ellerman.id.au \
    --cc=oleg@redhat.com \
    --cc=serge@hallyn.com \
    --cc=torvalds@linux-foundation.org \
    --cc=tyhicks@linux.microsoft.com \
    --cc=wad@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 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.