diff options
| author | Vladimir Oltean <vladimir.oltean@nxp.com> | 2022-03-03 18:42:49 +0300 |
|---|---|---|
| committer | Jakub Kicinski <kuba@kernel.org> | 2022-03-03 19:39:12 +0300 |
| commit | e1bec7fa1cee311a6d3fb9161037c7675904134d (patch) | |
| tree | f49f30d6e5be6f5851e16d0bd4a2d2c2bc03a097 /net/xfrm/xfrm_hash.c | |
| parent | 6c7273a266759d9d36f7c862149f248bcdeddc0f (diff) | |
| download | linux-e1bec7fa1cee311a6d3fb9161037c7675904134d.tar.xz | |
net: dsa: make dsa_tree_change_tag_proto actually unwind the tag proto change
The blamed commit said one thing but did another. It explains that we
should restore the "return err" to the original "goto out_unwind_tagger",
but instead it replaced it with "goto out_unlock".
When DSA_NOTIFIER_TAG_PROTO fails after the first switch of a
multi-switch tree, the switches would end up not using the same tagging
protocol.
Fixes: 0b0e2ff10356 ("net: dsa: restore error path of dsa_tree_change_tag_proto")
Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
Link: https://lore.kernel.org/r/20220303154249.1854436-1-vladimir.oltean@nxp.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'net/xfrm/xfrm_hash.c')
0 files changed, 0 insertions, 0 deletions