From: Leon Hwang <leon.hwang@linux.dev>
To: Yonghong Song <yonghong.song@linux.dev>, bpf@vger.kernel.org
Cc: Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Eduard Zingerman <eddyz87@gmail.com>,
kernel-team@fb.com
Subject: Re: [PATCH bpf-next v4 0/3] bpf: Fix trampoline handling of 128-bit values
Date: Tue, 28 Jul 2026 12:22:41 +0800 [thread overview]
Message-ID: <1c4223ae-a5ba-48a4-95d3-57c8ff241055@linux.dev> (raw)
In-Reply-To: <20260728035437.3007984-1-yonghong.song@linux.dev>
On 28/7/26 11:54, Yonghong Song 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.
>
> Changelogs:
> v3 -> v4:
> - v3: https://lore.kernel.org/bpf/20260710225206.4013062-1-yonghong.song@linux.dev/
> - Add Ack from Leon Hwang
Seems you changed my tag from Acked-by to Reviewed-by.
No worries, Reviewed-by is fine with me.
> v2 -> v3:
> - v2: https://lore.kernel.org/bpf/20260710182204.1085329-1-yonghong.song@linux.dev/
> - Align __int128 argument at even position enforced by arm64.
> v1 -> v2:
> - v1: https://lore.kernel.org/bpf/20260710144404.2579671-1-yonghong.song@linux.dev/
> - Also handle __int128 arguments for x86_64.
>
> Yonghong Song (3):
> bpf: Reject >8 byte return values on return-reading trampoline paths
> bpf, x86: Fix trampoline stack size for 128-bit arguments
> selftests/bpf: Add tests for >8 byte return value and 128-bit
> arguments
>
> arch/x86/net/bpf_jit_comp.c | 7 ++--
> kernel/bpf/bpf_struct_ops.c | 12 +++++++
> kernel/bpf/verifier.c | 25 +++++++++++++
> .../bpf/prog_tests/tracing_failure.c | 12 +++++++
> .../selftests/bpf/prog_tests/tracing_struct.c | 36 +++++++++++++++++++
> .../selftests/bpf/progs/tracing_failure.c | 6 ++++
> .../bpf/progs/tracing_struct_int128.c | 18 ++++++++++
> .../selftests/bpf/test_kmods/bpf_testmod.c | 32 +++++++++++++++++
> 8 files changed, 143 insertions(+), 5 deletions(-)
> create mode 100644 tools/testing/selftests/bpf/progs/tracing_struct_int128.c
>
next prev parent reply other threads:[~2026-07-28 4:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 3:54 [PATCH bpf-next v4 0/3] bpf: Fix trampoline handling of 128-bit values Yonghong Song
2026-07-28 3:54 ` [PATCH bpf-next v4 1/3] bpf: Reject >8 byte return values on return-reading trampoline paths Yonghong Song
2026-07-28 3:54 ` [PATCH bpf-next v4 2/3] bpf, x86: Fix trampoline stack size for 128-bit arguments Yonghong Song
2026-07-28 3:54 ` [PATCH bpf-next v4 3/3] selftests/bpf: Add tests for >8 byte return value and " Yonghong Song
2026-07-28 4:22 ` Leon Hwang [this message]
2026-07-28 5:06 ` [PATCH bpf-next v4 0/3] bpf: Fix trampoline handling of 128-bit values Yonghong Song
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=1c4223ae-a5ba-48a4-95d3-57c8ff241055@linux.dev \
--to=leon.hwang@linux.dev \
--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