From: Daniel Borkmann <daniel@iogearbox.net>
To: Shubham Bansal <illusionist.neo@gmail.com>,
Kees Cook <keescook@chromium.org>
Cc: kernel-hardening@lists.openwall.com, "Reshetova,
Elena" <elena.reshetova@intel.com>
Subject: Re: [kernel-hardening] Looking for something to WORK ON
Date: Wed, 11 Jan 2017 23:39:50 +0100 [thread overview]
Message-ID: <5876B436.1040308@iogearbox.net> (raw)
In-Reply-To: <CAHgaXdLA-mNQh3Tb-m2=uKKL3JYsstAvDsK3dp+d1TifrinioA@mail.gmail.com>
On 01/11/2017 11:12 PM, Shubham Bansal wrote:
> Hi Kees,
>
> I would have already started working on it since we last talked but before
> that I wanted to check if anybody else is also not working on the same
> thing. Otherwise it would be waste of time.
>
> Anyways. I will start working on it. No point in postponing in.
Very sorry for the late reply, Shubham, seems I missed your earlier email. :/
Afaik, nobody is working on that, so would be nice to tackle this.
> On Jan 12, 2017 2:59 AM, "Kees Cook" <keescook@chromium.org> wrote:
>
>> On Wed, Jan 11, 2017 at 4:46 AM, Shubham Bansal
>> <illusionist.neo@gmail.com> wrote:
>>>
>>> On Wed, Jul 13, 2016 at 2:32 PM, Daniel Borkmann <daniel@iogearbox.net>
>>> wrote:
>>>> Feel free to check out slides etc that are mostly located here:
>>>>
>>>> https://github.com/iovisor/bpf-docs
>>>>
>>>> Also, Documentation/networking/filter.txt in the kernel tree provides
>> some
>>>> info as a starting point, an example of eBPF JIT can be found here
>>>> arch/x86/net/
>>>> in kernel tree.
>>>>
>>>> To give you a basic overview what JITs are still classic BPF (cBPF)
>> ones:
>>>>
>>>> $ git grep -n "select HAVE_CBPF_JIT"
>>>> arch/arm/Kconfig:44: select HAVE_CBPF_JIT
>>>> arch/mips/Kconfig:18: select HAVE_CBPF_JIT if !CPU_MICROMIPS
>>>> arch/powerpc/Kconfig:131: select HAVE_CBPF_JIT if CPU_BIG_ENDIAN
>>>> arch/sparc/Kconfig:35: select HAVE_CBPF_JIT
>>>>
>>>> ... and which are eBPF (ppc64 one should get merged next window I
>>>> believe):
>>>>
>>>> $ git grep -n "select HAVE_EBPF_JIT"
>>>> arch/arm64/Kconfig:64: select HAVE_EBPF_JIT
>>>> arch/s390/Kconfig:131: select HAVE_EBPF_JIT if PACK_STACK &&
>>>> HAVE_MARCH_Z196_FEATURES
>>>> arch/x86/Kconfig:94: select HAVE_EBPF_JIT if
>> X86_64
>>>>
>>>> Cheers,
>>>> Daniel
>>>
>>> Hi Daniel,
>>>
>>> I have read about the EBPF and BFP. I wanted to start contributing. Do
>> you
>>> have any place for me to start with ?
>>> I mailed you regarding the same few months ago but didn't get the reply.
>>
>> Daniel may have more ideas, but I would say taking a CBPF jit and
>> converting it to an EBPF jit would be the best thing to start with.
>>
>> Doing ARM first might be easiest to tackle?
>>
>> -Kees
>>
>> --
>> Kees Cook
>> Nexus Security
>>
>
next prev parent reply other threads:[~2017-01-11 22:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 14:40 [kernel-hardening] Looking for something to WORK ON Shubham Bansal
2016-07-06 15:14 ` Sandy Harris
2016-07-10 16:42 ` Shubham Bansal
2016-07-10 19:29 ` Stephan Mueller
2016-07-06 17:35 ` Kees Cook
2016-07-10 16:04 ` Shubham Bansal
2016-07-11 18:52 ` Kees Cook
2016-07-12 13:25 ` Shubham Bansal
2016-07-12 17:17 ` Kees Cook
2016-07-12 17:36 ` Mark Rutland
2016-07-12 18:45 ` Kees Cook
2016-07-13 7:37 ` Shubham Bansal
2016-07-13 9:02 ` Daniel Borkmann
2017-01-11 12:46 ` Shubham Bansal
2017-01-11 21:29 ` Kees Cook
2017-01-11 22:12 ` Shubham Bansal
2017-01-11 22:39 ` Daniel Borkmann [this message]
2017-01-12 16:19 ` Shubham Bansal
2016-07-11 19:05 ` Valdis.Kletnieks
2016-07-11 19:14 ` Kees Cook
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=5876B436.1040308@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=elena.reshetova@intel.com \
--cc=illusionist.neo@gmail.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.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 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.