diff options
| author | Vladimir Oltean <[email protected]> | 2021-06-29 20:32:15 +0000 |
|---|---|---|
| committer | David S. Miller <[email protected]> | 2021-07-01 18:29:42 +0000 |
| commit | b71d09871566a20ae8a1064e50f1e94813b18482 (patch) | |
| tree | 6bdd2fe53cb76839265930e2b65cd20099ede840 /net/unix/af_unix.c | |
| parent | Merge branch 'octeopntx2-LMTST-regions' (diff) | |
| download | kernel-b71d09871566a20ae8a1064e50f1e94813b18482.tar.gz kernel-b71d09871566a20ae8a1064e50f1e94813b18482.zip | |
net: dsa: return -EOPNOTSUPP when driver does not implement .port_lag_join
The DSA core has a layered structure, and even though we end up
returning 0 (success) to user space when setting a bonding/team upper
that can't be offloaded, some parts of the framework actually need to
know that we couldn't offload that.
For example, if dsa_switch_lag_join returns 0 as it currently does,
dsa_port_lag_join has no way to tell a successful offload from a
software fallback, and it will call dsa_port_bridge_join afterwards.
Then we'll think we're offloading the bridge master of the LAG, when in
fact we're not even offloading the LAG. In turn, this will make us set
skb->offload_fwd_mark = true, which is incorrect and the bridge doesn't
like it.
Signed-off-by: Vladimir Oltean <[email protected]>
Reviewed-by: Florian Fainelli <[email protected]>
Signed-off-by: David S. Miller <[email protected]>
Diffstat (limited to 'net/unix/af_unix.c')
0 files changed, 0 insertions, 0 deletions