diff options
| author | Jakub Kicinski <[email protected]> | 2023-07-21 03:23:23 +0000 |
|---|---|---|
| committer | Jakub Kicinski <[email protected]> | 2023-07-21 03:23:23 +0000 |
| commit | bf837e8f7df873a6bb8a472550b1876100c60ddc (patch) | |
| tree | 4da7bcbc76c9a1727ade2934ed1859aa82828c1b /net/switchdev/switchdev.c | |
| parent | Merge branch 'eth-bnxt-handle-invalid-tx-completions-more-gracefully' (diff) | |
| parent | selftests: net: Add test cases for nexthop groups with invalid neighbors (diff) | |
| download | kernel-bf837e8f7df873a6bb8a472550b1876100c60ddc.tar.gz kernel-bf837e8f7df873a6bb8a472550b1876100c60ddc.zip | |
Merge branch 'nexthop-refactor-and-fix-nexthop-selection-for-multipath-routes'
Benjamin Poirier says:
====================
nexthop: Refactor and fix nexthop selection for multipath routes
In order to select a nexthop for multipath routes, fib_select_multipath()
is used with legacy nexthops and nexthop_select_path_hthr() is used with
nexthop objects. Those two functions perform a validity test on the
neighbor related to each nexthop but their logic is structured differently.
This causes a divergence in behavior and nexthop_select_path_hthr() may
return a nexthop that failed the neighbor validity test even if there was
one that passed.
Refactor nexthop_select_path_hthr() to make it more similar to
fib_select_multipath() and fix the problem mentioned above.
v1: https://lore.kernel.org/netdev/[email protected]/
====================
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Jakub Kicinski <[email protected]>
Diffstat (limited to 'net/switchdev/switchdev.c')
0 files changed, 0 insertions, 0 deletions