From: keescook@google.com (Kees Cook)
To: linux-arm-kernel@lists.infradead.org
Subject: arch: arm: bpf: Converting cBPF to eBPF for arm 32 bit
Date: Tue, 23 May 2017 12:32:59 -0700 [thread overview]
Message-ID: <CAGXu5j+DZ7+5zBh7s82AZPgDT=-WHo8bG6XwPT6SzaMtVMMn_Q@mail.gmail.com> (raw)
In-Reply-To: <CAHgaXdJa9uJYO3bODuzDRaqOas0i=zMk0jioWFXKm_=UJRtVrw@mail.gmail.com>
On Tue, May 23, 2017 at 11:39 AM, Shubham Bansal
<illusionist.neo@gmail.com> wrote:
> Here is the patch I sent to the arm mailing list.
Thanks for sending this!
I'm trying to figure out the best way to split this up, but the bulk
of it (the actual JIT changes) seems like they need to all land at the
same time. Any thoughts on this Daniel?
-Kees
--
Kees Cook
Pixel Security
next prev parent reply other threads:[~2017-05-23 19:32 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHgaXdKsO2xoKYp7g91g+n+d_1KHSSByLjzBB-WjVXSjhB7qxw@mail.gmail.com>
[not found] ` <20170510.212952.1440495072777358778.davem@davemloft.net>
[not found] ` <CAHgaXdK8LEEUPm4jTRRzCnjwdWAauHmmB=caZsSFY8MmStH89Q@mail.gmail.com>
[not found] ` <20170510.215218.2185526627014393313.davem@davemloft.net>
[not found] ` <CAHgaXdKZ_v+iO7uqEDx7PA7D+xcp1FngGvJ1SRSsGXNQ-iWWDQ@mail.gmail.com>
2017-05-11 9:32 ` arch: arm: bpf: Converting cBPF to eBPF for arm 32 bit Shubham Bansal
2017-05-11 15:30 ` Kees Cook
2017-05-13 21:38 ` Shubham Bansal
2017-05-15 17:44 ` Kees Cook
2017-05-15 19:55 ` Daniel Borkmann
2017-05-20 20:01 ` Shubham Bansal
2017-05-22 13:01 ` Daniel Borkmann
2017-05-22 17:04 ` Shubham Bansal
2017-05-22 20:05 ` Kees Cook
2017-05-23 2:58 ` Shubham Bansal
2017-05-23 4:27 ` Kees Cook
2017-05-22 18:58 ` Kees Cook
2017-05-22 19:08 ` Florian Fainelli
2017-05-23 3:34 ` Shubham Bansal
2017-05-23 4:22 ` Kees Cook
2017-05-23 5:03 ` Shubham Bansal
2017-05-23 5:35 ` Kees Cook
[not found] ` <CAHgaXdJa9uJYO3bODuzDRaqOas0i=zMk0jioWFXKm_=UJRtVrw@mail.gmail.com>
2017-05-23 19:32 ` Kees Cook [this message]
2017-01-30 10:38 Shubham Bansal
2017-01-30 21:57 ` Kees Cook
[not found] ` <CAHgaXd+nj69n-Xf46N=4M-j-0hKHVrrLfsvRZCG=2CCAtVF6ZA@mail.gmail.com>
[not found] ` <CAGXu5j+NSLomuSgD40kys+pWc+J9aB6Bbk_gSP9Lp_ScimQn_w@mail.gmail.com>
2017-02-01 13:01 ` Shubham Bansal
[not found] ` <76621BFF-B30B-4417-AB2B-DB21CA6092D9@netronome.com>
2017-02-03 7:04 ` Shubham Bansal
2017-02-03 8:25 ` nick viljoen
2017-02-08 7:29 ` Shubham Bansal
2017-02-08 19:41 ` Kees Cook
2017-03-15 12:13 ` Shubham Bansal
2017-03-15 21:55 ` David Miller
2017-03-28 20:49 ` Shubham Bansal
2017-03-29 0:00 ` Daniel Borkmann
2017-03-30 14:04 ` Shubham Bansal
2017-04-06 11:05 ` Shubham Bansal
2017-04-06 12:51 ` Daniel Borkmann
2017-05-06 16:48 ` Shubham Bansal
2017-05-06 18:38 ` David Miller
2017-05-06 20:27 ` Shubham Bansal
2017-05-06 22:17 ` Shubham Bansal
2017-05-09 20:12 ` Shubham Bansal
2017-05-09 20:19 ` David Miller
2017-05-09 20:25 ` Daniel Borkmann
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='CAGXu5j+DZ7+5zBh7s82AZPgDT=-WHo8bG6XwPT6SzaMtVMMn_Q@mail.gmail.com' \
--to=keescook@google.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).