diff options
| author | Florian Fainelli <f.fainelli@gmail.com> | 2018-05-15 16:01:24 -0700 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2018-05-16 14:11:22 -0400 |
| commit | 6c05561c541843b2bec2189f680bed6d20afc25b (patch) | |
| tree | 894df56cec85e31331ae9d327571f0756f804eb6 /drivers/clocksource/bcm_kona_timer.c | |
| parent | 43a5e00f38fe8933a1c716bfe5b30e97f749d94b (diff) | |
| download | linux-6c05561c541843b2bec2189f680bed6d20afc25b.tar.gz linux-6c05561c541843b2bec2189f680bed6d20afc25b.tar.bz2 linux-6c05561c541843b2bec2189f680bed6d20afc25b.zip | |
net: dsa: bcm_sf2: Fix IPv6 rules and chain ID
We had several issues that would make the programming of IPv6 rules both
inconsistent and error prone:
- the chain ID that we would be asking the hardware to put in the
packet's Broadcom tag would be off by one, it would return one of the
two indexes, but not the one user-space specified
- when an user specified a particular location to insert a CFP rule at,
we would not be returning the same index, which would be confusing if
nothing else
- finally, like IPv4, it would be possible to overflow the last entry by
re-programming it
Fix this by swapping the usage of rule_index[0] and rule_index[1] where
relevant in order to return a consistent and correct user-space
experience.
Fixes: ba0696c22e7c ("net: dsa: bcm_sf2: Add support for IPv6 CFP rules")
Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/clocksource/bcm_kona_timer.c')
0 files changed, 0 insertions, 0 deletions