[PATCH net-next 0/2] net: dsa: mv88e6xxx: ethtool n-tuple follow ups

[Jakub Kicinski <kuba@kernel.org>]

Here are two small tweaks to the mv88e6xxx n-tuple filter handling
suggested by Sashiko when reviewing commit b1fffc273112 ("net: dsa:
mv88e6xxx: bound the policy rule dump by the caller's buffer size")

At the high level the problem is that the driver has shared rule
table but for some ops it doesn't check whether the rule operated
on belongs to the port on which the ethtool request was sent.

I initially thought that this could be intentional, but on closer
look I don't think it really works..

Sending for net-next, because this is AI-induced, build-tested-only
slop-code. The outcome is unlikely and results in mis-configuration,
no crashes.

Jakub Kicinski (2):
  net: dsa: mv88e6xxx: check the port when reading back a policy rule
  net: dsa: mv88e6xxx: check the port when deleting a policy rule

 drivers/net/dsa/mv88e6xxx/chip.c | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

-- 
2.55.0