diff options
| author |   Maciej Fijalkowski <maciej.fijalkowski@intel.com> | 2022-04-13 17:30:13 +0200 |
|---|---|---|
| committer |   Daniel Borkmann <daniel@iogearbox.net> | 2022-04-15 21:11:05 +0200 |
| commit | a817ead4154d86c74bf98936f3a385e8a21974ff (patch) | |
| tree | 11102ce30e3c135958b532e7afb1ed322045de22 /tools/testing/selftests/bpf/prog_tests/test_strncmp.c | |
| parent | mlx5, xsk: Diversify return values from xsk_wakeup call paths (diff) | |
| download | linux-dev-a817ead4154d86c74bf98936f3a385e8a21974ff.tar.xz linux-dev-a817ead4154d86c74bf98936f3a385e8a21974ff.zip | |
stmmac, xsk: Diversify return values from xsk_wakeup call paths
Currently, when debugging AF_XDP workloads, one can correlate the -ENXIO
return code as the case that XSK is not in the bound state. Returning
same code from ndo_xsk_wakeup can be misleading and simply makes it
harder to follow what is going on.
Change ENXIOs in stmmac's ndo_xsk_wakeup() implementation to EINVALs, so
that when probing it is clear that something is wrong on the driver
side, not the xsk_{recv,send}msg.
There is a -ENETDOWN that can happen from both kernel/driver sides
though, but I don't have a correct replacement for this on one of the
sides, so let's keep it that way.
Signed-off-by: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Link: https://lore.kernel.org/bpf/20220413153015.453864-13-maciej.fijalkowski@intel.com
Diffstat (limited to 'tools/testing/selftests/bpf/prog_tests/test_strncmp.c')
0 files changed, 0 insertions, 0 deletions