netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Borkmann <dborkman@redhat.com>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: Xi Wang <xi.wang@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	Russell King <linux@arm.linux.org.uk>,
	Eric Dumazet <edumazet@google.com>,
	Will Drewry <wad@chromium.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	Nicolas Schichan <nschichan@freebox.fr>,
	Mircea Gherzan <mgherzan@gmail.com>
Subject: Re: [RFC PATCH net-next 0/6] seccomp filter JIT
Date: Fri, 26 Apr 2013 13:46:29 +0200	[thread overview]
Message-ID: <517A6915.2020208@redhat.com> (raw)
In-Reply-To: <20130426112539.GA3736@osiris>

On 04/26/2013 01:25 PM, Heiko Carstens wrote:
> On Fri, Apr 26, 2013 at 03:51:40AM -0400, Xi Wang wrote:
>> This patchset brings JIT support to seccomp filters for x86_64 and ARM.
>> It is against the net-next tree.
>>
>> The current BPF JIT interface only accepts sk_filter, not seccomp_filter.
>> Patch 1/6 refactors the interface to make it more general.
>>
>> With the refactored interface, patches 2/6 and 3/6 implement the seccomp
>> BPF_S_ANC_SECCOMP_LD_W instruction in x86 & ARM JIT.
>>
>> Status:
>>
>> * x86_64 & ARM: JIT tested with seccomp examples.
>>
>> * powerpc [4/6]: no seccomp change - compile checked.
>>
>> * sparc [5/6] & s390 [6/6]: no seccomp change - untested.
>>
>> Sorry I have no sparc or s390 build environment here.  Can someone help
>> check 5/6 and 6/6?  Thanks.
>
> Your patches are against which tree?
> They don't apply on top of linux-next or Linus' linux tree.

In the subject line it says net-next.

> Btw. are there any test cases around for BPF JIT?
> Not only for the new seccomp but also netfilter?

BPF is used in packet(7) sockets, not Netfilter. But yeah, test
cases for different archs would be really good, i.e. if seccomp
wants to use BPF JIT, where seccomp is used for user space program
sand-boxing (e.g. in Chromium), I can already guess that this will
put attention to certain people. :-)

I think BPF JIT for seccomp on ARM recently got applied to -mm tree
if I'm not mistaken. It was from Nicolas Schichan (cc):

http://thread.gmane.org/gmane.linux.ports.arm.kernel/233416/

  parent reply	other threads:[~2013-04-26 11:46 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-26  7:51 [RFC PATCH net-next 0/6] seccomp filter JIT Xi Wang
2013-04-26  7:51 ` [RFC PATCH net-next 1/6] filter: refactor BPF JIT for seccomp filters Xi Wang
2013-04-26 15:20   ` Eric Dumazet
2013-04-26  7:51 ` [RFC PATCH net-next 2/6] x86: bpf_jit_comp: support BPF_S_ANC_SECCOMP_LD_W instruction Xi Wang
2013-04-26 14:18   ` Eric Dumazet
2013-04-26 14:50     ` Xi Wang
2013-04-26 15:11       ` Eric Dumazet
2013-04-26 15:29         ` Xi Wang
2013-04-26 15:43           ` Eric Dumazet
2013-04-26 15:57             ` Xi Wang
2013-04-26 18:48             ` David Miller
2013-04-26 16:02         ` Xi Wang
2013-04-26 16:14           ` Eric Dumazet
2013-04-26 18:25             ` Xi Wang
2013-04-26 18:40               ` Eric Dumazet
2013-04-26 15:15       ` David Laight
2013-04-26 15:27         ` Eric Dumazet
2013-04-26 15:38           ` David Laight
2013-04-26 15:46             ` Eric Dumazet
2013-04-26  7:51 ` [RFC PATCH net-next 3/6] ARM: net: bpf_jit_32: " Xi Wang
2013-04-26  7:51 ` [RFC PATCH net-next 4/6] PPC: net: bpf_jit_comp: refactor the BPF JIT interface Xi Wang
2013-04-26  7:51 ` [RFC PATCH net-next 5/6] sparc: " Xi Wang
2013-04-26  7:51 ` [RFC PATCH net-next 6/6] s390/bpf,jit: " Xi Wang
2013-04-26 11:25 ` [RFC PATCH net-next 0/6] seccomp filter JIT Heiko Carstens
2013-04-26 11:46   ` Heiko Carstens
2013-04-26 12:15     ` Xi Wang
2013-04-26 11:46   ` Daniel Borkmann [this message]
2013-04-26 12:31     ` Xi Wang
2013-04-26 12:38       ` Daniel Borkmann
2013-04-29 12:18       ` Nicolas Schichan
2013-04-29 13:21         ` 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=517A6915.2020208@redhat.com \
    --to=dborkman@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mgherzan@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=nschichan@freebox.fr \
    --cc=wad@chromium.org \
    --cc=xi.wang@gmail.com \
    /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).