BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Yonghong Song <yonghong.song@linux.dev>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
	daniel@iogearbox.net, eddyz87@gmail.com, kernel-team@fb.com
Subject: Re: [PATCH bpf-next v5 0/3] bpf: Fix trampoline handling of 128-bit values
Date: Sat, 01 Aug 2026 01:10:12 +0000	[thread overview]
Message-ID: <178554661214.974239.3202155911510305468.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260729050154.2585468-1-yonghong.song@linux.dev>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Kumar Kartikeya Dwivedi <memxor@gmail.com>:

On Tue, 28 Jul 2026 22:01:54 -0700 you wrote:
> The BPF trampoline preserves only 8 bytes of a target function's return
> value (R0), and its register save area under-allocates space for 128-bit
> arguments for x86_64. These two problems lead to memory corruption or
> incorrect values observed by BPF programs and the real caller.
> 
> This series fixes both issues and adds two selftests, otherwise, each of
> them will fail if without the corresponding fix.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v5,1/3] bpf: Reject >8 byte return values on return-reading trampoline paths
    https://git.kernel.org/bpf/bpf-next/c/c48796aa6c39
  - [bpf-next,v5,2/3] bpf, x86: Fix trampoline stack size for 128-bit arguments
    https://git.kernel.org/bpf/bpf-next/c/814cba835ef6
  - [bpf-next,v5,3/3] selftests/bpf: Add tests for >8 byte return value and 128-bit arguments
    https://git.kernel.org/bpf/bpf-next/c/13cc6b788b1a

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-08-01  1:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-29  5:01 [PATCH bpf-next v5 0/3] bpf: Fix trampoline handling of 128-bit values Yonghong Song
2026-07-29  5:01 ` [PATCH bpf-next v5 1/3] bpf: Reject >8 byte return values on return-reading trampoline paths Yonghong Song
2026-07-29  5:02 ` [PATCH bpf-next v5 2/3] bpf, x86: Fix trampoline stack size for 128-bit arguments Yonghong Song
2026-07-29  6:20   ` bot+bpf-ci
2026-08-01  0:57     ` Yonghong Song
2026-07-29  5:02 ` [PATCH bpf-next v5 3/3] selftests/bpf: Add tests for >8 byte return value and " Yonghong Song
2026-08-01  1:10 ` 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=178554661214.974239.3202155911510305468.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=kernel-team@fb.com \
    --cc=yonghong.song@linux.dev \
    /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