From: Kees Cook <keescook@chromium.org>
To: David Abdurachmanov <david.abdurachmanov@gmail.com>
Cc: Tycho Andersen <tycho@tycho.ws>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@sifive.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Oleg Nesterov <oleg@redhat.com>,
Andy Lutomirski <luto@amacapital.net>,
Will Drewry <wad@chromium.org>, Shuah Khan <shuah@kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Martin KaFai Lau <kafai@fb.com>, Song Liu <songliubraving@fb.com>,
Yonghong Song <yhs@fb.com>,
David Abdurachmanov <david.abdurachmanov@sifive.com>,
Thomas Gleixner <tglx@linutronix.de>,
Allison Randal <allison@lohutok.net>,
Alexios Zavras <alexios.zavras@intel.com>,
Anup Patel <Anup.Patel@wdc.com>,
Vincent Chen <vincentc@andestech.com>,
Alan Kao <alankao@andestech.com>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, netdev@vger.kernel.org,
bpf@vger.kernel.org, me@carlosedp.com
Subject: Re: [PATCH v2] riscv: add support for SECCOMP and SECCOMP_FILTER
Date: Mon, 26 Aug 2019 10:48:34 -0700 [thread overview]
Message-ID: <201908261043.08510F5E66@keescook> (raw)
In-Reply-To: <CAEn-LTrtn01=fp6taBBG_QkfBtgiJyt6oUjZJOi6VN8OeXp6=g@mail.gmail.com>
On Mon, Aug 26, 2019 at 09:39:50AM -0700, David Abdurachmanov wrote:
> I don't have the a build with SECCOMP for the board right now, so it
> will have to wait. I just finished a new kernel (almost rc6) for Fedora,
FWIW, I don't think this should block landing the code: all the tests
fail without seccomp support. ;) So this patch is an improvement!
--
Kees Cook
next prev parent reply other threads:[~2019-08-28 17:37 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-22 20:55 [PATCH v2] riscv: add support for SECCOMP and SECCOMP_FILTER David Abdurachmanov
2019-08-23 22:54 ` Carlos Eduardo de Paula
2019-08-23 23:01 ` Carlos Eduardo de Paula
2019-08-24 0:30 ` Paul Walmsley
2019-08-24 1:04 ` David Abdurachmanov
2019-08-24 1:10 ` David Abdurachmanov
2019-08-24 1:18 ` Paul Walmsley
2019-08-25 21:51 ` Kees Cook
2019-08-28 21:39 ` David Abdurachmanov
2019-08-26 14:57 ` Tycho Andersen
2019-08-26 16:39 ` David Abdurachmanov
2019-08-26 17:48 ` Kees Cook [this message]
2019-08-29 1:30 ` Paul Walmsley
2019-09-27 17:20 ` Kees Cook
2019-10-05 1:24 ` Paul Walmsley
2019-08-25 21:59 ` Kees Cook
2019-08-28 17:52 ` Andy Lutomirski
2019-08-28 18:01 ` Kees Cook
2019-09-03 22:27 ` Palmer Dabbelt
2019-09-27 20:58 ` Andy Lutomirski
2019-10-06 19:18 ` Andy Lutomirski
2019-08-28 21:37 ` David Abdurachmanov
2019-08-28 23:44 ` Kees Cook
2019-10-05 1:20 ` Paul Walmsley
2019-10-14 21:06 ` Paul Walmsley
2019-10-15 16:27 ` Kees Cook
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=201908261043.08510F5E66@keescook \
--to=keescook@chromium.org \
--cc=Anup.Patel@wdc.com \
--cc=alankao@andestech.com \
--cc=alexios.zavras@intel.com \
--cc=allison@lohutok.net \
--cc=aou@eecs.berkeley.edu \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=david.abdurachmanov@gmail.com \
--cc=david.abdurachmanov@sifive.com \
--cc=kafai@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=luto@amacapital.net \
--cc=me@carlosedp.com \
--cc=netdev@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=palmer@sifive.com \
--cc=paul.walmsley@sifive.com \
--cc=shuah@kernel.org \
--cc=songliubraving@fb.com \
--cc=tglx@linutronix.de \
--cc=tycho@tycho.ws \
--cc=vincentc@andestech.com \
--cc=wad@chromium.org \
--cc=yhs@fb.com \
/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).