linux-riscv.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Paul Walmsley <paul.walmsley@sifive.com>
To: torvalds@linux-foundation.org
Cc: david.abdurachmanov@sifive.com, linux-riscv@lists.infradead.org,
	keescook@chromium.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] RISC-V SECCOMP support for v5.4-rc5
Date: Tue, 22 Oct 2019 16:03:08 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.21.9999.1910221600320.25457@viisi.sifive.com> (raw)

Linus,

The following changes since commit 5bf4e52ff0317db083fafee010dc806f8d4cb0cb:

  RISC-V: fix virtual address overlapped in FIXADDR_START and VMEMMAP_START (2019-10-15 22:47:41 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git tags/riscv/for-v5.4-rc5

for you to fetch changes up to 7326fcbeea619b95c9b380ddee0a94f5f9ea6a48:

  riscv: add support for SECCOMP and SECCOMP_FILTER (2019-10-16 08:27:25 -0700)

----------------------------------------------------------------
RISC-V SECCOMP support for v5.4-rc5

This pull request contains a single change: the addition of SECCOMP
support for RISC-V for v5.4-rc5.  Normally, I'd consider this too
large for this point in the -rc releases.  However, we've heard that
v5.4 is likely to be a long-term support release, and adding it in now
should help the distribution and security folks.  The changes look
relatively bounded, and the only reason we've been sitting on it until
now is because we've been waiting for a trivial ack from the
tools/testing maintainer.  That hasn't come.  Since the change to that
subsystem is quite minor, we think it should be OK with her, so,
sending it now.

If you have a different opinion about whether this patch should go in
now, we're fine with requeuing it for v5.5-rc1.

----------------------------------------------------------------
David Abdurachmanov (1):
      riscv: add support for SECCOMP and SECCOMP_FILTER

 arch/riscv/Kconfig                            | 14 ++++++++++++++
 arch/riscv/include/asm/seccomp.h              | 10 ++++++++++
 arch/riscv/include/asm/thread_info.h          |  5 ++++-
 arch/riscv/kernel/entry.S                     | 27 +++++++++++++++++++++++++--
 arch/riscv/kernel/ptrace.c                    | 10 ++++++++++
 tools/testing/selftests/seccomp/seccomp_bpf.c |  8 +++++++-
 6 files changed, 70 insertions(+), 4 deletions(-)
 create mode 100644 arch/riscv/include/asm/seccomp.h

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

                 reply	other threads:[~2019-10-22 23:03 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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.DEB.2.21.9999.1910221600320.25457@viisi.sifive.com \
    --to=paul.walmsley@sifive.com \
    --cc=david.abdurachmanov@sifive.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).