From: hpa@zytor.com (H. Peter Anvin)
To: linux-arm-kernel@lists.infradead.org
Subject: Post-merge-window ping (Re: [PATCH v4 0/5] x86: two-phase syscall tracing and seccomp fastpath)
Date: Fri, 05 Sep 2014 13:43:44 -0700 [thread overview]
Message-ID: <540A2080.8050404@zytor.com> (raw)
In-Reply-To: <540A1800.3000005@zytor.com>
On 09/05/2014 01:07 PM, H. Peter Anvin wrote:
> On 08/26/2014 06:32 PM, Andy Lutomirski wrote:
>> On Mon, Jul 28, 2014 at 8:38 PM, Andy Lutomirski <luto@amacapital.net> wrote:
>>> This applies to:
>>> git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git seccomp-fastpath
>>>
>>> Gitweb:
>>> https://git.kernel.org/cgit/linux/kernel/git/kees/linux.git/log/?h=seccomp/fastpath
>>
>> Hi all-
>>
>> AFAIK the only thing that's changed since I submitted it is that the
>> 3.17 merge window is closed. Kees rebased the tree this applies to,
>> but I think the patches all still apply. What, if anything, do I need
>> to do to help this along for 3.18?
>>
>
> Just put this stuff in a branch and running through my personal test
> battery now.
>
... and they fail build testing. Specifically, both i386 and x86-64
allnoconfig fail with:
arch/x86/kernel/ptrace.c: In function ?syscall_trace_enter_phase2?:
LD fs/quota/built-in.o
../arch/x86/kernel/ptrace.c:1579:2: error: implicit declaration of
function ?seccomp_phase2? [-Werror=implicit-function-declaration]
if (phase1_result > 1 && seccomp_phase2(phase1_result)) {
^
cc1: some warnings being treated as errors
CC arch/x86/kernel/step.o
make[4]: *** [arch/x86/kernel/ptrace.o] Error 1
-hpa
next prev parent reply other threads:[~2014-09-05 20:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-27 1:32 Post-merge-window ping (Re: [PATCH v4 0/5] x86: two-phase syscall tracing and seccomp fastpath) Andy Lutomirski
2014-08-27 1:45 ` Alexei Starovoitov
2014-09-05 20:07 ` H. Peter Anvin
2014-09-05 20:43 ` H. Peter Anvin [this message]
2014-09-05 21:14 ` Andy Lutomirski
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=540A2080.8050404@zytor.com \
--to=hpa@zytor.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox