diff options
author | Magnus Karlsson <[email protected]> | 2023-01-25 08:48:58 +0100 |
---|---|---|
committer | Jakub Kicinski <[email protected]> | 2023-01-27 22:27:59 -0800 |
commit | 12b5717990c81fc2f6f2aa9d53d960b916478d4f (patch) | |
tree | b59aabfb0507f8f797bdc146555661663fa145c6 /tools/testing/selftests/bpf/prog_tests/autoload.c | |
parent | 2ccce20d51faa0178086163ccb6c84a099a87ab4 (diff) |
lan966x: execute xdp_do_flush() before napi_complete_done()
Make sure that xdp_do_flush() is always executed before
napi_complete_done(). This is important for two reasons. First, a
redirect to an XSKMAP assumes that a call to xdp_do_redirect() from
napi context X on CPU Y will be followed by a xdp_do_flush() from the
same napi context and CPU. This is not guaranteed if the
napi_complete_done() is executed before xdp_do_flush(), as it tells
the napi logic that it is fine to schedule napi context X on another
CPU. Details from a production system triggering this bug using the
veth driver can be found following the first link below.
The second reason is that the XDP_REDIRECT logic in itself relies on
being inside a single NAPI instance through to the xdp_do_flush() call
for RCU protection of all in-kernel data structures. Details can be
found in the second link below.
Fixes: a825b611c7c1 ("net: lan966x: Add support for XDP_REDIRECT")
Signed-off-by: Magnus Karlsson <[email protected]>
Acked-by: Toke Høiland-Jørgensen <[email protected]>
Acked-by: Steen Hegelund <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Link: https://lore.kernel.org/all/[email protected]/
Signed-off-by: Jakub Kicinski <[email protected]>
Diffstat (limited to 'tools/testing/selftests/bpf/prog_tests/autoload.c')
0 files changed, 0 insertions, 0 deletions