[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGXu5j+N5Du=c-dfGd-_rLjE3NEeN+MXTsKjt2APA1U1xwwSag@mail.gmail.com>
Date: Wed, 24 Oct 2018 15:34:45 -0700
From: Kees Cook <keescook@...omium.org>
To: Palmer Dabbelt <palmer@...ive.com>
Cc: linux-riscv@...ts.infradead.org, Albert Ou <aou@...s.berkeley.edu>,
Paul Moore <paul@...l-moore.com>,
Eric Paris <eparis@...hat.com>,
Andy Lutomirski <luto@...capital.net>,
Will Drewry <wad@...omium.org>,
Wesley Terpstra <wesley@...ive.com>,
David Howells <dhowells@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>,
Philippe Ombredanne <pombredanne@...b.com>,
Greg KH <gregkh@...uxfoundation.org>,
Kate Stewart <kstewart@...uxfoundation.org>,
LKML <linux-kernel@...r.kernel.org>,
Linux Audit <linux-audit@...hat.com>,
david.abdurachmanov@...il.com
Subject: Re: [PATCH 2/2] RISC-V: Add support for SECCOMP
On Wed, Oct 24, 2018 at 2:42 PM, Kees Cook <keescook@...omium.org> wrote:
> config HAVE_ARCH_SECCOMP_FILTER
> bool
> help
> An arch should select this symbol if it provides all of these things:
> - syscall_get_arch()
> - syscall_get_arguments()
> - syscall_rollback()
> - syscall_set_return_value()
> - SIGSYS siginfo_t support
> - secure_computing is called from a ptrace_event()-safe context
> - secure_computing return value is checked and a return value of -1
> results in the system call being skipped immediately.
> - seccomp syscall wired up
Oh, and I should add to this list, "passes
tools/testing/selftests/seccomp/seccomp_bpf test". :)
--
Kees Cook
Powered by blists - more mailing lists