From: dborkman@redhat.com (Daniel Borkmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V3 2/3] ARM: net: bpf_jit: make code generation less dependent on struct sk_filter.
Date: Fri, 26 Apr 2013 21:47:46 +0200 [thread overview]
Message-ID: <517AD9E2.2090704@redhat.com> (raw)
In-Reply-To: <20130426122601.10ec05fcb4860df1b0a5b409@linux-foundation.org>
On 04/26/2013 09:26 PM, Andrew Morton wrote:
> On Fri, 26 Apr 2013 16:04:44 +0200 Arnd Bergmann <arnd@arndb.de> wrote:
>> On Wednesday 24 April 2013 19:27:08 Nicolas Schichan wrote:
>>> @@ -858,7 +858,7 @@ b_epilogue:
>>> }
>>>
>>>
>>> -void bpf_jit_compile(struct sk_filter *fp)
>>> +static void __bpf_jit_compile(struct jit_ctx *out_ctx)
>>> {
>>> struct jit_ctx ctx;
>>> unsigned tmp_idx;
>>> @@ -867,11 +867,10 @@ void bpf_jit_compile(struct sk_filter *fp)
>>> if (!bpf_jit_enable)
>>> return;
>>>
>>> - memset(&ctx, 0, sizeof(ctx));
>>> - ctx.skf = fp;
>>> + ctx = *out_ctx;
>>> ctx.ret0_fp_idx = -1;
>>>
>>> - ctx.offsets = kzalloc(4 * (ctx.skf->len + 1), GFP_KERNEL);
>>> + ctx.offsets = kzalloc(4 * (ctx.prog_len + 1), GFP_KERNEL);
>>> if (ctx.offsets == NULL)
>>> return;
>>>
>>> @@ -921,13 +920,26 @@ void bpf_jit_compile(struct sk_filter *fp)
>>> print_hex_dump(KERN_INFO, "BPF JIT code: ",
>>> DUMP_PREFIX_ADDRESS, 16, 4, ctx.target,
>>> alloc_size, false);
>>> -
>>> - fp->bpf_func = (void *)ctx.target;
>>> out:
>>> kfree(ctx.offsets);
>>> +
>>> + *out_ctx = ctx;
>>> return;
>>
>> This part of the patch, in combination with 79617801e "filter: bpf_jit_comp:
>> refactor and unify BPF JIT image dump output" is now causing build errors
>> in linux-next:
>>
>> arch/arm/net/bpf_jit_32.c: In function '__bpf_jit_compile':
>> arch/arm/net/bpf_jit_32.c:930:16: error: 'fp' undeclared (first use in this function)
>> bpf_jit_dump(fp->len, alloc_size, 2, ctx.target);
>
> Thanks, I did this. There may be a smarter way...
I think also seccomp_jit_compile() would need this change then, otherwise the build
with CONFIG_SECCOMP_FILTER_JIT might break.
I can fix this up for you if not already applied. I presume it's against
linux-next tree?
> --- a/arch/arm/net/bpf_jit_32.c~arm-net-bpf_jit-make-code-generation-less-dependent-on-struct-sk_filter-fix
> +++ a/arch/arm/net/bpf_jit_32.c
> @@ -858,7 +858,7 @@ b_epilogue:
> }
>
>
> -static void __bpf_jit_compile(struct jit_ctx *out_ctx)
> +static void __bpf_jit_compile(struct sk_filter *fp, struct jit_ctx *out_ctx)
> {
> struct jit_ctx ctx;
> unsigned tmp_idx;
> @@ -934,7 +934,7 @@ void bpf_jit_compile(struct sk_filter *f
> ctx.prog_len = fp->len;
> ctx.prog_insns = fp->insns;
>
> - __bpf_jit_compile(&ctx);
> + __bpf_jit_compile(fp, &ctx);
> if (ctx.target)
> fp->bpf_func = (void *)ctx.target;
> }
> _
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2013-04-26 19:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-24 17:27 [PATCH V3] Support for JIT in Seccomp BPF filters Nicolas Schichan
2013-04-24 17:27 ` [PATCH V3 1/3] seccomp: add generic code for jitted seccomp filters Nicolas Schichan
2013-04-24 17:27 ` [PATCH V3 2/3] ARM: net: bpf_jit: make code generation less dependent on struct sk_filter Nicolas Schichan
2013-04-24 17:41 ` Daniel Borkmann
2013-04-26 14:04 ` Arnd Bergmann
2013-04-26 19:26 ` Andrew Morton
2013-04-26 19:47 ` Daniel Borkmann [this message]
2013-04-26 20:09 ` Andrew Morton
2013-04-26 22:01 ` Daniel Borkmann
2013-04-26 22:18 ` Xi Wang
2013-04-26 22:30 ` Daniel Borkmann
2013-04-26 23:33 ` David Miller
2013-04-24 17:27 ` [PATCH V3 3/3] ARM: net: bpf_jit: add support for jitted seccomp filters Nicolas Schichan
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=517AD9E2.2090704@redhat.com \
--to=dborkman@redhat.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;
as well as URLs for NNTP newsgroup(s).