From: patchwork-bot+netdevbpf@kernel.org
To: Piotr Krysiuk <piotras@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, paulburton@kernel.org,
johan.almbladh@anyfinetworks.com, tsbogend@alpha.franken.de
Subject: Re: [PATCH] bpf, mips: Validate conditional branch offsets
Date: Wed, 15 Sep 2021 19:50:06 +0000 [thread overview]
Message-ID: <163173540691.23489.15401014246279305631.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210915160437.4080-1-piotras@gmail.com>
Hello:
This patch was applied to bpf/bpf.git (refs/heads/master):
On Wed, 15 Sep 2021 17:04:37 +0100 you wrote:
> The conditional branch instructions on MIPS use 18-bit signed offsets
> allowing for a branch range of 128 KBytes (backward and forward).
> However, this limit is not observed by the cBPF JIT compiler, and so
> the JIT compiler emits out-of-range branches when translating certain
> cBPF programs. A specific example of such a cBPF program is included in
> the "BPF_MAXINSNS: exec all MSH" test from lib/test_bpf.c that executes
> anomalous machine code containing incorrect branch offsets under JIT.
>
> [...]
Here is the summary with links:
- bpf, mips: Validate conditional branch offsets
https://git.kernel.org/bpf/bpf/c/37cb28ec7d3a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-09-15 19:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 16:04 [PATCH] bpf, mips: Validate conditional branch offsets Piotr Krysiuk
2021-09-15 17:38 ` Johan Almbladh
2021-09-15 19:50 ` patchwork-bot+netdevbpf [this message]
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=163173540691.23489.15401014246279305631.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=johan.almbladh@anyfinetworks.com \
--cc=paulburton@kernel.org \
--cc=piotras@gmail.com \
--cc=tsbogend@alpha.franken.de \
/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.