From: David Abdurachmanov <david.abdurachmanov@gmail.com>
To: Kees Cook <keescook@chromium.org>
Cc: aou@eecs.berkeley.edu, Will Drewry <wad@chromium.org>,
Palmer Dabbelt <palmer@sifive.com>,
linux-kernel@vger.kernel.org, luto@amacapital.net,
Green Hu <green.hu@gmail.com>,
linux-riscv@lists.infradead.org, deanbo422@gmail.com
Subject: Re: [PATCH 1/2] riscv: add support for SECCOMP incl. filters
Date: Thu, 6 Dec 2018 18:12:54 +0100 [thread overview]
Message-ID: <CAEn-LTpVeULecL3JGRDjQcdZTh9yfqXsrirrxcAamYdX2jRkew@mail.gmail.com> (raw)
In-Reply-To: <CAGXu5jKevZHDW8hRAAh_muFUXsg-WOVCYh3HczjY5qKtR=wYNg@mail.gmail.com>
On Thu, Dec 6, 2018 at 6:07 PM Kees Cook <keescook@chromium.org> wrote:
>
> On Thu, Dec 6, 2018 at 7:02 AM David Abdurachmanov
> <david.abdurachmanov@gmail.com> wrote:
> > The patch adds support for SECCOMP and SECCOMP_FILTER (BPF).
>
> I built this against linux-next but it's missing seccomp.h. Was that
> accidentally left out of the commit?
>
>
> CC arch/riscv/kernel/asm-offsets.s
> In file included from ./include/linux/sched.h:21:0,
> from arch/riscv/kernel/asm-offsets.c:18:
> ./include/linux/seccomp.h:14:10: fatal error: asm/seccomp.h: No such
> file or directory
> #include <asm/seccomp.h>
> ^~~~~~~~~~~~~~~
>
I forgot to add it...
Will fix it.
david
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2018-12-06 17:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-06 15:01 [PATCH 0/2] riscv: add support for SECCOMP and SECCOMP_FILTER David Abdurachmanov
2018-12-06 15:01 ` [PATCH 1/2] riscv: add support for SECCOMP incl. filters David Abdurachmanov
2018-12-06 16:47 ` Kees Cook
2018-12-06 17:10 ` David Abdurachmanov
2018-12-06 16:51 ` Kees Cook
2018-12-06 17:11 ` David Abdurachmanov
2018-12-06 18:25 ` David Abdurachmanov
2018-12-06 18:32 ` Kees Cook
2018-12-06 17:06 ` Kees Cook
2018-12-06 17:12 ` David Abdurachmanov [this message]
2018-12-06 15:01 ` [PATCH 2/2] riscv: fix syscall_{get,set}_arguments David Abdurachmanov
2018-12-06 16:48 ` Kees Cook
2018-12-06 17:13 ` David Abdurachmanov
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=CAEn-LTpVeULecL3JGRDjQcdZTh9yfqXsrirrxcAamYdX2jRkew@mail.gmail.com \
--to=david.abdurachmanov@gmail.com \
--cc=aou@eecs.berkeley.edu \
--cc=deanbo422@gmail.com \
--cc=green.hu@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=luto@amacapital.net \
--cc=palmer@sifive.com \
--cc=wad@chromium.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).