diff options
| author | Alexei Starovoitov <ast@kernel.org> | 2026-10-21 00:09:21 +0000 |
|---|---|---|
| committer | Alexei Starovoitov <ast@kernel.org> | 2026-10-21 17:50:51 +0000 |
| commit | cce4e11eea2dc517e5222dae500bd38182d041c4 (patch) | |
| tree | e980ae8e914ececac5faa2f21e674524fbb9e357 /scripts/basic/split-include.c | |
| parent | 60e1e9f03ba733285f4e39c0b6f7220b6fd52d80 (diff) | |
| parent | 4c2cdb6156920b5fb578779b5da62edf3fc45556 (diff) | |
| download | linux-cce4e11eea2dc517e5222dae500bd38182d041c4.tar.gz linux-cce4e11eea2dc517e5222dae500bd38182d041c4.zip | |
Merge branch 'bpf-fixes-for-unwind_goto-and-unwind_exit'
Alexei Starovoitov says:
====================
bpf: Fixes for unwind_goto and unwind_exit
From: Alexei Starovoitov <ast@kernel.org>
Two fixes for what the bots found in v4 [1] of the series that added
unwind_goto and unwind_exit.
Patch 1. unwind_exit of an exception callback is exit for the verifier, but
JITs looked up the return address. The callback returns from the frame of
the main prog. After freplace or a tail call that's a return to a prog, and
the callback could end up in a pad that wasn't verified with it.
It came with 'unwind_exit of an async or an exception callback is exit' in
v4. For an async callback that's fine: it has a frame of its own.
Patch 2. Offloaded progs with the new insns are rejected.
Patch 3. Tests for patch 1. They fail without it.
[1] https://lore.kernel.org/bpf/20261020181320.1284798-1-alexei.starovoitov@gmail.com/
====================
Link: https://patch.msgid.link/20261020231942.2568163-1-alexei.starovoitov@gmail.com
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Diffstat (limited to 'scripts/basic/split-include.c')
0 files changed, 0 insertions, 0 deletions
