From: Kees Cook <keescook@chromium.org>
To: Paul Walmsley <paul.walmsley@sifive.com>
Cc: linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
David Abdurachmanov <david.abdurachmanov@gmail.com>,
Andy Lutomirski <luto@amacapital.net>,
Oleg Nesterov <oleg@redhat.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Keith Packard <keith.packard@sifive.com>,
Tycho Andersen <tycho@tycho.ws>
Subject: Re: [PATCH] riscv: fix seccomp reject syscall code path
Date: Mon, 2 Mar 2020 20:46:46 -0800 [thread overview]
Message-ID: <202003022042.2A99B9B0@keescook> (raw)
In-Reply-To: <20200223171757.GB22040@cisco>
On Sun, Feb 23, 2020 at 10:17:57AM -0700, Tycho Andersen wrote:
> On Sat, Feb 08, 2020 at 08:18:17AM -0700, Tycho Andersen wrote:
> > ...
>
> Ping, any risc-v people have thoughts on this?
>
> Tycho
Re-ping. :) Can someone please pick this up? Original patch here:
https://lore.kernel.org/lkml/20200208151817.12383-1-tycho@tycho.ws/
--
Kees Cook
WARNING: multiple messages have this Message-ID (diff)
From: Kees Cook <keescook@chromium.org>
To: Paul Walmsley <paul.walmsley@sifive.com>
Cc: Tycho Andersen <tycho@tycho.ws>,
Albert Ou <aou@eecs.berkeley.edu>,
David Abdurachmanov <david.abdurachmanov@gmail.com>,
linux-kernel@vger.kernel.org, Oleg Nesterov <oleg@redhat.com>,
Andy Lutomirski <luto@amacapital.net>,
Keith Packard <keith.packard@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
linux-riscv@lists.infradead.org
Subject: Re: [PATCH] riscv: fix seccomp reject syscall code path
Date: Mon, 2 Mar 2020 20:46:46 -0800 [thread overview]
Message-ID: <202003022042.2A99B9B0@keescook> (raw)
In-Reply-To: <20200223171757.GB22040@cisco>
On Sun, Feb 23, 2020 at 10:17:57AM -0700, Tycho Andersen wrote:
> On Sat, Feb 08, 2020 at 08:18:17AM -0700, Tycho Andersen wrote:
> > ...
>
> Ping, any risc-v people have thoughts on this?
>
> Tycho
Re-ping. :) Can someone please pick this up? Original patch here:
https://lore.kernel.org/lkml/20200208151817.12383-1-tycho@tycho.ws/
--
Kees Cook
next prev parent reply other threads:[~2020-03-03 4:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-08 15:18 [PATCH] riscv: fix seccomp reject syscall code path Tycho Andersen
2020-02-08 15:18 ` Tycho Andersen
2020-02-10 1:11 ` Kees Cook
2020-02-10 1:11 ` Kees Cook
2020-02-23 17:17 ` Tycho Andersen
2020-02-23 17:17 ` Tycho Andersen
2020-03-03 4:46 ` Kees Cook [this message]
2020-03-03 4:46 ` Kees Cook
2020-03-03 17:55 ` Palmer Dabbelt
2020-03-03 17:55 ` Palmer Dabbelt
2020-03-03 21:12 ` Kees Cook
2020-03-03 21:12 ` Kees Cook
2020-03-06 0:02 ` Palmer Dabbelt
2020-03-06 0:02 ` Palmer Dabbelt
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=202003022042.2A99B9B0@keescook \
--to=keescook@chromium.org \
--cc=aou@eecs.berkeley.edu \
--cc=david.abdurachmanov@gmail.com \
--cc=keith.packard@sifive.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=luto@amacapital.net \
--cc=oleg@redhat.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=tycho@tycho.ws \
/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.