From: Rob Landley <rob@landley.net>
To: linux-sh@vger.kernel.org
Subject: Re: Adding support for SECCOMP_FILTER
Date: Wed, 22 Jul 2020 03:13:13 +0000 [thread overview]
Message-ID: <bd4f0ecf-d5f9-ee1e-d58e-85db2fdda25a@landley.net> (raw)
In-Reply-To: <32f7f7a2-a186-a3cc-0d03-e3380c0d21fc@physik.fu-berlin.de>
On 7/21/20 1:59 PM, John Paul Adrian Glaubitz wrote:
> Hello!
>
> I recently discovered that the kernel supports seccomp on Linux as support
> was added in 2.6.27 [1].
>
> I consequently added SH support to libseccomp [2], only to discover that we
> are missing the SECCOMP_FILTER feature. Looking at the changes for PA-RISC [3]
> and RISC-V [4], the necessary changes in the kernel seem to be rather modest.
>
> Would anyone be willing to help me to implement SECCOMP_FILTER for SH? From what
> I can see, we just need to implement the part to add syscall filtering.
I dunno how much help I'd be (never having used seccomp), but I can try to
reproduce what you do on a second setup? :)
Rob
next prev parent reply other threads:[~2020-07-22 3:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 18:59 Adding support for SECCOMP_FILTER John Paul Adrian Glaubitz
2020-07-22 3:13 ` Rob Landley [this message]
2020-07-22 23:31 ` John Paul Adrian Glaubitz
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=bd4f0ecf-d5f9-ee1e-d58e-85db2fdda25a@landley.net \
--to=rob@landley.net \
--cc=linux-sh@vger.kernel.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).