From: Daniel Borkmann <daniel@iogearbox.net>
To: Shubham Bansal <illusionist.neo@gmail.com>
Cc: Kees Cook <keescook@chromium.org>,
Network Development <netdev@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Alexei Starovoitov <ast@kernel.org>,
Russell King <linux@armlinux.org.uk>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
LKML <linux-kernel@vger.kernel.org>, Andrew Lunn <andrew@lunn.ch>
Subject: Re: [PATCH v2] arm: eBPF JIT compiler
Date: Tue, 13 Jun 2017 01:17:14 +0200 [thread overview]
Message-ID: <593F20FA.6010505@iogearbox.net> (raw)
In-Reply-To: <CAHgaXd+DW2bggto=2S9hOdMrtPTvhD2QN4rPf2V8iHewQpg-YA@mail.gmail.com>
On 06/12/2017 05:40 PM, Shubham Bansal wrote:
[...]
>> Did you manage to get tail calls tested as well (I assume so since you
>> implemented emit_bpf_tail_call() in the patch but just out of curiosity)?
>
> I didn't try it exclusively, I thought test_bpf must have tested it. Doesn't it?
In samples/bpf/ there's sockex3* that would exercise it, or
alternatively in iproute2 repo under examples/bpf/ there's
bpf_cyclic.c and bpf_tailcall.c as a prog.
Hm, generally, we should really add a test case also to BPF
selftest suite to facilitate that. I'll likely do that for
the next batch of BPF patches.
next prev parent reply other threads:[~2017-06-12 23:17 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1495754003-21099-1-git-send-email-illusionist.neo@gmail.com>
2017-05-30 19:19 ` [PATCH v2] arm: eBPF JIT compiler Kees Cook
2017-06-06 19:47 ` Shubham Bansal
2017-06-12 2:00 ` Kees Cook
2017-06-12 10:21 ` Daniel Borkmann
2017-06-12 11:06 ` Russell King - ARM Linux
2017-06-12 15:41 ` Shubham Bansal
2017-06-12 15:40 ` Shubham Bansal
2017-06-12 22:45 ` Alexander Alemayhu
2017-06-12 22:47 ` David Miller
2017-06-12 23:17 ` Daniel Borkmann [this message]
2017-06-13 6:56 ` Shubham Bansal
2017-06-14 20:31 ` Daniel Borkmann
2017-06-17 12:23 ` Shubham Bansal
2017-06-19 18:10 ` Daniel Borkmann
2017-06-20 1:34 ` Shubham Bansal
2017-06-20 16:55 ` Daniel Borkmann
2017-06-21 14:26 ` Shubham Bansal
2017-06-21 16:32 ` Daniel Borkmann
2017-06-21 19:37 ` Shubham Bansal
2017-06-21 19:53 ` Daniel Borkmann
2017-06-23 22:39 ` Shubham Bansal
2017-07-05 22:11 ` Kees Cook
2017-07-05 22:38 ` Kees Cook
2017-07-06 3:49 ` Shubham Bansal
2017-07-07 4:42 ` Kees Cook
2017-07-07 4:49 ` Shubham Bansal
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=593F20FA.6010505@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=andrew@lunn.ch \
--cc=ast@kernel.org \
--cc=davem@davemloft.net \
--cc=illusionist.neo@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.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).