diff options
author | Alexei Starovoitov <ast@kernel.org> | 2021-09-26 23:07:28 +0300 |
---|---|---|
committer | Alexei Starovoitov <ast@kernel.org> | 2021-09-26 23:07:28 +0300 |
commit | e7d5184b24fb131b6ffc77cf84cd2d7d0d814b68 (patch) | |
tree | dbea750e919a475e18b051f991552847ec0b65ff /net/xdp/xsk_buff_pool.c | |
parent | 091037fb770e1771a52246f9b68dc76082178a3c (diff) | |
parent | ef979017b837031cbe3f2f7a4d78b00c48dc770b (diff) | |
download | linux-e7d5184b24fb131b6ffc77cf84cd2d7d0d814b68.tar.xz |
Merge branch 'bpf: Support <8-byte scalar spill and refill'
Martin KaFai says:
====================
The verifier currently does not save the reg state when
spilling <8byte bounded scalar to the stack. The bpf program
will be incorrectly rejected when this scalar is refilled to
the reg and then used to offset into a packet header.
The later patch has a simplified bpf prog from a real use case
to demonstrate this case. The current work around is
to reparse the packet again such that this offset scalar
is close to where the packet data will be accessed to
avoid the spill. Thus, the header is parsed twice.
The llvm patch [1] will align the <8bytes spill to
the 8-byte stack address. This set is to make the necessary
changes in verifier to support <8byte scalar spill and refill.
[1] https://reviews.llvm.org/D109073
v2:
- Changed the xdpwall selftest in patch 3 to trigger a u32
spill at a non 8-byte aligned stack address. The v1 has
simplified the real example too much such that it only
triggers a u32 spill but does not spill at a non
8-byte aligned stack address.
- Changed README.rst in patch 3 to explain the llvm dependency
for the xdpwall test.
====================
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Diffstat (limited to 'net/xdp/xsk_buff_pool.c')
0 files changed, 0 insertions, 0 deletions