[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1366989636.8964.214.camel@edumazet-glaptop>
Date: Fri, 26 Apr 2013 08:20:36 -0700
From: Eric Dumazet <eric.dumazet@...il.com>
To: Xi Wang <xi.wang@...il.com>
Cc: Daniel Borkmann <dborkman@...hat.com>,
"David S. Miller" <davem@...emloft.net>,
Russell King <linux@....linux.org.uk>,
Heiko Carstens <heiko.carstens@...ibm.com>,
Eric Dumazet <edumazet@...gle.com>,
Will Drewry <wad@...omium.org>,
Andrew Morton <akpm@...ux-foundation.org>,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH net-next 1/6] filter: refactor BPF JIT for seccomp
filters
On Fri, 2013-04-26 at 03:51 -0400, Xi Wang wrote:
> Currently, bpf_jit_compile() and bpf_jit_free() takes an sk_filter,
> which seccomp filters cannot reuse.
>
> Change bpf_jit_compile() to take a pointer to BPF instructions and
> the length, and to return a JITted function.
>
> Change bpf_jit_free() to take a JITted function.
>
> Add JIT calls for seccomp filters.
>
> Signed-off-by: Xi Wang <xi.wang@...il.com>
> ---
When submitting a patch serie, full kernel must be fully compile-able
after each patch.
Thats mandatory to be able to perform git bisection in the future.
You cannot change the prototypes as you do in this patch, because it
breaks all the BPF JIT.
arch/x86/net/bpf_jit_comp.c:147:6: error: conflicting types for ‘bpf_jit_compile’
include/linux/filter.h:57:19: note: previous declaration of ‘bpf_jit_compile’ was here
arch/x86/net/bpf_jit_comp.c:749:6: error: conflicting types for ‘bpf_jit_free’
include/linux/filter.h:58:13: note: previous declaration of ‘bpf_jit_free’ was here
make[1]: *** [arch/x86/net/bpf_jit_comp.o] Error 1
make: *** [arch/x86/net/bpf_jit_comp.o] Error 2
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists