From: Daniel Borkmann <daniel@iogearbox.net>
To: Paul Burton <paulburton@kernel.org>
Cc: "Paul Chaignon" <paul.chaignon@orange.com>,
"Björn Töpel" <bjorn.topel@gmail.com>,
"Mahshid Khezri" <khezri.mahshid@gmail.com>,
paul.chaignon@gmail.com, bpf@vger.kernel.org,
netdev@vger.kernel.org, "Alexei Starovoitov" <ast@kernel.org>,
"Martin KaFai Lau" <kafai@fb.com>,
"Song Liu" <songliubraving@fb.com>, "Yonghong Song" <yhs@fb.com>,
"Andrii Nakryiko" <andriin@fb.com>
Subject: Re: [PATCH bpf 2/2] bpf, mips: limit to 33 tail calls
Date: Thu, 12 Dec 2019 17:19:22 +0100 [thread overview]
Message-ID: <20191212161922.GA1264@localhost.localdomain> (raw)
In-Reply-To: <20191210232316.aastpgbirqp4yaoi@lantea.localdomain>
On Tue, Dec 10, 2019 at 03:23:16PM -0800, Paul Burton wrote:
> On Mon, Dec 09, 2019 at 07:52:52PM +0100, Paul Chaignon wrote:
> > All BPF JIT compilers except RISC-V's and MIPS' enforce a 33-tail calls
> > limit at runtime. In addition, a test was recently added, in tailcalls2,
> > to check this limit.
> >
> > This patch updates the tail call limit in MIPS' JIT compiler to allow
> > 33 tail calls.
> >
> > Fixes: b6bd53f9c4e8 ("MIPS: Add missing file for eBPF JIT.")
> > Reported-by: Mahshid Khezri <khezri.mahshid@gmail.com>
> > Signed-off-by: Paul Chaignon <paul.chaignon@orange.com>
>
> I'd be happy to take this through mips-fixes, but equally happy for it
> to go through the BPF/net trees in which case:
We took the series via bpf, thanks!
next prev parent reply other threads:[~2019-12-12 16:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 18:51 [PATCH bpf 0/2] Limit tail calls to 33 in all JIT compilers Paul Chaignon
2019-12-09 18:52 ` [PATCH bpf 1/2] bpf, riscv: limit to 33 tail calls Paul Chaignon
2019-12-09 19:57 ` Björn Töpel
2019-12-10 6:31 ` Björn Töpel
2019-12-10 9:36 ` Paul Chaignon
2019-12-09 18:52 ` [PATCH bpf 2/2] bpf, mips: " Paul Chaignon
2019-12-10 23:23 ` Paul Burton
2019-12-12 16:19 ` Daniel Borkmann [this message]
2019-12-18 9:32 ` Alexander Lobakin
2019-12-18 9:58 ` Paul Chaignon
2019-12-18 10:02 ` Alexander Lobakin
2019-12-10 18:19 ` [PATCH bpf 0/2] Limit tail calls to 33 in all JIT compilers Martin Lau
2019-12-11 13:00 ` 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=20191212161922.GA1264@localhost.localdomain \
--to=daniel@iogearbox.net \
--cc=andriin@fb.com \
--cc=ast@kernel.org \
--cc=bjorn.topel@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=kafai@fb.com \
--cc=khezri.mahshid@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=paul.chaignon@gmail.com \
--cc=paul.chaignon@orange.com \
--cc=paulburton@kernel.org \
--cc=songliubraving@fb.com \
--cc=yhs@fb.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).