From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: bpf@vger.kernel.org, ast@kernel.org, puranjay@kernel.org,
xukuohai@huaweicloud.com
Subject: Re: [PATCH bpf 1/2] bpf, arm64, insn: Reject out-of-range B.cond targets
Date: Wed, 15 Apr 2026 19:20:18 +0000 [thread overview]
Message-ID: <177628081879.2402333.2608299227037618336.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260415121403.639619-1-daniel@iogearbox.net>
Hello:
This series was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Wed, 15 Apr 2026 14:14:02 +0200 you wrote:
> aarch64_insn_gen_cond_branch_imm() calls label_imm_common() to
> compute a 19-bit signed byte offset for a conditional branch,
> but unlike its siblings aarch64_insn_gen_branch_imm() and
> aarch64_insn_gen_comp_branch_imm(), it does not check whether
> label_imm_common() returned its out-of-range sentinel (range)
> before feeding the value to aarch64_insn_encode_immediate().
>
> [...]
Here is the summary with links:
- [bpf,1/2] bpf, arm64, insn: Reject out-of-range B.cond targets
https://git.kernel.org/bpf/bpf/c/48d83d94930e
- [bpf,2/2] bpf, arm64: Fix off-by-one in check_imm signed range check
https://git.kernel.org/bpf/bpf/c/1dd8be4ec722
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:[~2026-04-15 19:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-15 12:14 [PATCH bpf 1/2] bpf, arm64, insn: Reject out-of-range B.cond targets Daniel Borkmann
2026-04-15 12:14 ` [PATCH bpf 2/2] bpf, arm64: Fix off-by-one in check_imm signed range check Daniel Borkmann
2026-04-15 19:20 ` 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=177628081879.2402333.2608299227037618336.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=puranjay@kernel.org \
--cc=xukuohai@huaweicloud.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