diff options
author | Magnus Karlsson <magnus.karlsson@intel.com> | 2023-01-25 08:49:01 +0100 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2023-02-09 11:28:05 +0100 |
commit | 9e0d874c0a6bda0cb77f2e5ac98afab3b4cf012d (patch) | |
tree | fe41d00933ec74745ddd6aa138ead66384d2c1e4 /net | |
parent | 71a773ab79c9911d306aa81a007492d2cb17bc5d (diff) | |
download | linux-riscv-9e0d874c0a6bda0cb77f2e5ac98afab3b4cf012d.tar.gz linux-riscv-9e0d874c0a6bda0cb77f2e5ac98afab3b4cf012d.tar.bz2 linux-riscv-9e0d874c0a6bda0cb77f2e5ac98afab3b4cf012d.zip |
dpaa2-eth: execute xdp_do_flush() before napi_complete_done()
[ Upstream commit a3191c4d86c5d3bd35b00dfde6910b88391436a0 ]
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: d678be1dc1ec ("dpaa2-eth: add XDP_REDIRECT support")
Signed-off-by: Magnus Karlsson <magnus.karlsson@intel.com>
Acked-by: Toke Høiland-Jørgensen <toke@redhat.com>
Link: https://lore.kernel.org/r/20221220185903.1105011-1-sbohrer@cloudflare.com
Link: https://lore.kernel.org/all/20210624160609.292325-1-toke@redhat.com/
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'net')
0 files changed, 0 insertions, 0 deletions