diff options
| author |   Hariprasad Kelam <hkelam@marvell.com> | 2025-05-20 11:39:52 +0530 |
|---|---|---|
| committer |   David S. Miller <davem@davemloft.net> | 2025-05-25 15:06:53 +0100 |
| commit | bb91f7547f79434e8818d3f235437e021d34c1cb (patch) | |
| tree | 36275a4e276841e4b07a10943a83612cfe6fca19 /scripts/gdb/linux/utils.py | |
| parent | Merge branch 'so_passrights' (diff) | |
| download | wireguard-linux-bb91f7547f79434e8818d3f235437e021d34c1cb.tar.xz wireguard-linux-bb91f7547f79434e8818d3f235437e021d34c1cb.zip | |
octeontx2-af: NPC: Clear Unicast rule on nixlf detach
The AF driver assigns reserved MCAM entries (for unicast, broadcast,
etc.) based on the NIXLF number. When a NIXLF is detached, these entries
are disabled.
For example,
PF NIXLF
--------------------
PF0 0
SDP-VF0 1
If the user unbinds both PF0 and SDP-VF0 interfaces and then binds them in
reverse order
PF NIXLF
---------------------
SDP-VF0 0
PF0 1
In this scenario, the PF0 unicast entry is getting corrupted because
the MCAM entry contains stale data (SDP-VF0 ucast data)
This patch resolves the issue by clearing the unicast MCAM entry during
NIXLF detach
Signed-off-by: Hariprasad Kelam <hkelam@marvell.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to '')
0 files changed, 0 insertions, 0 deletions