BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Yazhou Tang <tangyazhou@zju.edu.cn>
Cc: bpf@vger.kernel.org, ast@kernel.org, eddyz87@gmail.com,
	emil@etsalapatis.com, puranjay@kernel.org,
	xukuohai@huaweicloud.com, qmo@kernel.org, daniel@iogearbox.net,
	john.fastabend@gmail.com, andrii@kernel.org,
	martin.lau@linux.dev, song@kernel.org, yonghong.song@linux.dev,
	kpsingh@kernel.org, sdf@fomichev.me, haoluo@google.com,
	jolsa@kernel.org, tangyazhou518@outlook.com,
	shenghaoyuan0928@163.com, ziye@zju.edu.cn
Subject: Re: [PATCH bpf-next v10 0/3] bpf: Fix call offset truncation and OOB read in bpf_patch_call_args()
Date: Mon, 11 May 2026 15:40:09 +0000	[thread overview]
Message-ID: <177851400930.2299654.13767981329926141065.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260506094714.419842-1-tangyazhou@zju.edu.cn>

Hello:

This series was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Wed,  6 May 2026 17:47:11 +0800 you wrote:
> From: Yazhou Tang <tangyazhou518@outlook.com>
> 
> This patchset addresses a silent truncation bug in the BPF verifier that
> occurs when a bpf-to-bpf call involves a massive relative jump offset.
> Additionally, it fixes a pre-existing out-of-bounds (OOB) read issue
> in the interpreter fallback path.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v10,1/3] bpf: Fix out-of-bounds read in bpf_patch_call_args()
    https://git.kernel.org/bpf/bpf/c/4314a44564eb
  - [bpf-next,v10,2/3] bpf: Fix s16 truncation for large bpf-to-bpf call offsets
    https://git.kernel.org/bpf/bpf/c/58a8f3e2501d
  - [bpf-next,v10,3/3] selftests/bpf: Add test for large offset bpf-to-bpf call
    https://git.kernel.org/bpf/bpf/c/344a00712ce1

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-05-11 15:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-06  9:47 [PATCH bpf-next v10 0/3] bpf: Fix call offset truncation and OOB read in bpf_patch_call_args() Yazhou Tang
2026-05-06  9:47 ` [PATCH bpf-next v10 1/3] bpf: Fix out-of-bounds " Yazhou Tang
2026-05-06  9:47 ` [PATCH bpf-next v10 2/3] bpf: Fix s16 truncation for large bpf-to-bpf call offsets Yazhou Tang
2026-05-06  9:47 ` [PATCH bpf-next v10 3/3] selftests/bpf: Add test for large offset bpf-to-bpf call Yazhou Tang
2026-05-11  8:28 ` [PATCH bpf-next v10 0/3] bpf: Fix call offset truncation and OOB read in bpf_patch_call_args() Yazhou Tang
2026-05-11 15:40 ` 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=177851400930.2299654.13767981329926141065.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=eddyz87@gmail.com \
    --cc=emil@etsalapatis.com \
    --cc=haoluo@google.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kpsingh@kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=puranjay@kernel.org \
    --cc=qmo@kernel.org \
    --cc=sdf@fomichev.me \
    --cc=shenghaoyuan0928@163.com \
    --cc=song@kernel.org \
    --cc=tangyazhou518@outlook.com \
    --cc=tangyazhou@zju.edu.cn \
    --cc=xukuohai@huaweicloud.com \
    --cc=yonghong.song@linux.dev \
    --cc=ziye@zju.edu.cn \
    /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