mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: James Morris <jmorris@namei.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-security-module@vger.kernel.org
Subject: [GIT PULL] security: seccomp changes for v4.21
Date: Mon, 31 Dec 2018 15:15:08 +1100 (AEDT)	[thread overview]
Message-ID: <alpine.LRH.2.21.1812311511360.1435@namei.org> (raw)

From Kees:

"- Add SECCOMP_RET_USER_NOTIF

- seccomp fixes for sparse warnings and s390 build (Tycho)"



The following changes since commit 1072bd678547f8663cfb81a22fdb50c589e4976e:

  security: fs: make inode explicitly non-modular (2018-12-12 14:58:51 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git next-seccomp

for you to fetch changes up to 55b8cbe470d103b44104c64dbf89e5cad525d4e0:

  Merge tag 'seccomp-next-part2' of https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux into next-seccomp (2018-12-17 11:36:26 -0800)

----------------------------------------------------------------
James Morris (2):
      Merge tag 'seccomp-next' of https://git.kernel.org/.../kees/linux into next-seccomp
      Merge tag 'seccomp-next-part2' of https://git.kernel.org/.../kees/linux into next-seccomp

Tycho Andersen (6):
      seccomp: hoist struct seccomp_data recalculation higher
      seccomp: switch system call argument type to void *
      seccomp: add a return code to trap to userspace
      samples: add an example of seccomp user trap
      seccomp: fix poor type promotion
      seccomp, s390: fix build for syscall type change

 Documentation/ioctl/ioctl-number.txt           |   1 +
 Documentation/userspace-api/seccomp_filter.rst |  84 +++++
 arch/s390/kernel/compat_wrapper.c              |   2 +-
 include/linux/seccomp.h                        |   9 +-
 include/linux/syscalls.h                       |   2 +-
 include/uapi/linux/seccomp.h                   |  40 ++-
 kernel/seccomp.c                               | 467 ++++++++++++++++++++++++-
 samples/seccomp/.gitignore                     |   1 +
 samples/seccomp/Makefile                       |   7 +-
 samples/seccomp/user-trap.c                    | 375 ++++++++++++++++++++
 tools/testing/selftests/seccomp/seccomp_bpf.c  | 447 ++++++++++++++++++++++-
 11 files changed, 1411 insertions(+), 24 deletions(-)
 create mode 100644 samples/seccomp/user-trap.c

             reply	other threads:[~2018-12-31  4:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-31  4:15 James Morris [this message]
2019-01-02 19:10 ` pr-tracker-bot
2019-01-07 10:15 ` Ingo Molnar
2019-01-07 20:03   ` James Morris
2019-01-07 21:09   ` Kees Cook
2019-01-07 21:53     ` Tycho Andersen
2019-01-07 22:04       ` Kees Cook
2019-01-08  6:46       ` Ingo Molnar

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=alpine.LRH.2.21.1812311511360.1435@namei.org \
    --to=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®