diff options
| author | Vladimir Oltean <vladimir.oltean@nxp.com> | 2021-06-29 17:06:52 +0300 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2021-06-29 10:46:23 -0700 |
| commit | 3f6e32f92a027e91f001070ec324dd3b534d948c (patch) | |
| tree | 7a7af9971a1c263d0939722e2f60485aa29e7d86 /crypto/arc4.c | |
| parent | 3dc80afc509831ec436e14d8ae74de330b37636d (diff) | |
| download | lwn-3f6e32f92a027e91f001070ec324dd3b534d948c.tar.gz lwn-3f6e32f92a027e91f001070ec324dd3b534d948c.zip | |
net: dsa: reference count the FDB addresses at the cross-chip notifier level
The same concerns expressed for host MDB entries are valid for host FDBs
just as well:
- in the case of multiple bridges spanning the same switch chip, deleting
a host FDB entry that belongs to one bridge will result in breakage to
the other bridge
- not deleting FDB entries across DSA links means that the switch's
hardware tables will eventually run out, given enough wear&tear
So do the same thing and introduce reference counting for CPU ports and
DSA links using the same data structures as we have for MDB entries.
Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'crypto/arc4.c')
0 files changed, 0 insertions, 0 deletions