All of lore.kernel.org
 help / color / mirror / Atom feed
From: Palmer Dabbelt <palmer@dabbelt.com>
To: keescook@chromium.org
Cc: Paul Walmsley <paul.walmsley@sifive.com>,
	linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
	david.abdurachmanov@gmail.com, luto@amacapital.net,
	oleg@redhat.com, aou@eecs.berkeley.edu, keith.packard@sifive.com,
	tycho@tycho.ws
Subject: Re: [PATCH] riscv: fix seccomp reject syscall code path
Date: Tue, 03 Mar 2020 09:55:10 -0800 (PST)	[thread overview]
Message-ID: <mhng-f926452f-8491-4deb-9721-a52487de676d@palmerdabbelt-glaptop1> (raw)
In-Reply-To: <202003022042.2A99B9B0@keescook>

On Mon, 02 Mar 2020 20:46:46 PST (-0800), keescook@chromium.org wrote:
> 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/

Sorry, the other messages didn't end up in my inbox.  I'll take a look, as this
seems like a good candidate for rc5.

WARNING: multiple messages have this Message-ID (diff)
From: Palmer Dabbelt <palmer@dabbelt.com>
To: keescook@chromium.org
Cc: tycho@tycho.ws, aou@eecs.berkeley.edu,
	david.abdurachmanov@gmail.com, linux-kernel@vger.kernel.org,
	oleg@redhat.com, luto@amacapital.net, keith.packard@sifive.com,
	Paul Walmsley <paul.walmsley@sifive.com>,
	linux-riscv@lists.infradead.org
Subject: Re: [PATCH] riscv: fix seccomp reject syscall code path
Date: Tue, 03 Mar 2020 09:55:10 -0800 (PST)	[thread overview]
Message-ID: <mhng-f926452f-8491-4deb-9721-a52487de676d@palmerdabbelt-glaptop1> (raw)
In-Reply-To: <202003022042.2A99B9B0@keescook>

On Mon, 02 Mar 2020 20:46:46 PST (-0800), keescook@chromium.org wrote:
> 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/

Sorry, the other messages didn't end up in my inbox.  I'll take a look, as this
seems like a good candidate for rc5.


  reply	other threads:[~2020-03-03 17:55 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
2020-03-03  4:46     ` Kees Cook
2020-03-03 17:55     ` Palmer Dabbelt [this message]
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=mhng-f926452f-8491-4deb-9721-a52487de676d@palmerdabbelt-glaptop1 \
    --to=palmer@dabbelt.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=david.abdurachmanov@gmail.com \
    --cc=keescook@chromium.org \
    --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=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.