From: luto@amacapital.net (Andy Lutomirski)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 0/4] arch/arm: support seccomp
Date: Tue, 13 Nov 2012 11:23:20 -0800 [thread overview]
Message-ID: <50A29E28.5040303@mit.edu> (raw)
In-Reply-To: <1352587485-18348-1-git-send-email-keescook@chromium.org>
On 11/10/2012 02:44 PM, Kees Cook wrote:
> This adds support for seccomp BPF to ARM. When built with the seccomp
> improvement patch waiting in linux-next ("seccomp: Make syscall skipping
> and nr changes more consistent"), this passes the seccomp regression
> test suite: https://github.com/redpig/seccomp
I don't know if this matters much on ARM, but should something like
https://git.kernel.org/?p=linux/kernel/git/luto/linux.git;a=commit;h=dee1ae5a05149f30baeccb4b8f68f22525ba9ca2
be added?
--Andy
>
> Thanks,
>
> -Kees
>
> ---
> v5:
> - clean up seccomp failure path, as requested by Will Deacon.
> v4:
> - fixed syscall_get_arch, thanks to Will Deacon.
> v3:
> - updates suggested by Russell King:
> - reduced scope of expansion
> - leveraged TIF_SYSCALL_WORK bit mask
> - fixed syscall==-1 short-circuit logic
> v2:
> - expanded ptrace_syscall_trace() into both callers and do
> secure_computing() hookup there, as requested by Al Viro.
>
WARNING: multiple messages have this Message-ID (diff)
From: Andy Lutomirski <luto@amacapital.net>
To: Kees Cook <keescook@chromium.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Russell King <linux@arm.linux.org.uk>,
Will Deacon <will.deacon@arm.com>,
Geremy Condra <gcondra@google.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Al Viro <viro@zeniv.linux.org.uk>, Will Drewry <wad@chromium.org>
Subject: Re: [PATCH v5 0/4] arch/arm: support seccomp
Date: Tue, 13 Nov 2012 11:23:20 -0800 [thread overview]
Message-ID: <50A29E28.5040303@mit.edu> (raw)
In-Reply-To: <1352587485-18348-1-git-send-email-keescook@chromium.org>
On 11/10/2012 02:44 PM, Kees Cook wrote:
> This adds support for seccomp BPF to ARM. When built with the seccomp
> improvement patch waiting in linux-next ("seccomp: Make syscall skipping
> and nr changes more consistent"), this passes the seccomp regression
> test suite: https://github.com/redpig/seccomp
I don't know if this matters much on ARM, but should something like
https://git.kernel.org/?p=linux/kernel/git/luto/linux.git;a=commit;h=dee1ae5a05149f30baeccb4b8f68f22525ba9ca2
be added?
--Andy
>
> Thanks,
>
> -Kees
>
> ---
> v5:
> - clean up seccomp failure path, as requested by Will Deacon.
> v4:
> - fixed syscall_get_arch, thanks to Will Deacon.
> v3:
> - updates suggested by Russell King:
> - reduced scope of expansion
> - leveraged TIF_SYSCALL_WORK bit mask
> - fixed syscall==-1 short-circuit logic
> v2:
> - expanded ptrace_syscall_trace() into both callers and do
> secure_computing() hookup there, as requested by Al Viro.
>
next prev parent reply other threads:[~2012-11-13 19:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-10 22:44 [PATCH v5 0/4] arch/arm: support seccomp Kees Cook
2012-11-10 22:44 ` Kees Cook
2012-11-10 22:44 ` [PATCH 1/4] arch/arm: add syscall_get_arch Kees Cook
2012-11-10 22:44 ` Kees Cook
2012-11-10 22:44 ` [PATCH 2/4] arch/arm: move secure_computing into trace Kees Cook
2012-11-10 22:44 ` Kees Cook
2012-11-10 22:44 ` [PATCH 3/4] arch/arm: allow a scno of -1 to not cause a SIGILL Kees Cook
2012-11-10 22:44 ` Kees Cook
2012-11-10 22:44 ` [PATCH 4/4] arch/arm: select HAVE_ARCH_SECCOMP_FILTER Kees Cook
2012-11-10 22:44 ` Kees Cook
2012-11-13 19:23 ` Andy Lutomirski [this message]
2012-11-13 19:23 ` [PATCH v5 0/4] arch/arm: support seccomp Andy Lutomirski
2012-11-14 19:05 ` Kees Cook
2012-11-14 19:05 ` Kees Cook
2012-11-14 19:07 ` Kees Cook
2012-11-14 19:07 ` Kees Cook
2012-11-15 13:25 ` Will Deacon
2012-11-15 13:25 ` Will Deacon
2012-11-15 20:23 ` Kees Cook
2012-11-15 20:23 ` Kees Cook
2012-11-15 21:02 ` Will Deacon
2012-11-15 21:02 ` Will Deacon
2012-11-15 20:34 ` Will Drewry
2012-11-15 20:34 ` Will Drewry
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=50A29E28.5040303@mit.edu \
--to=luto@amacapital.net \
--cc=linux-arm-kernel@lists.infradead.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 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.