From: Or Gerlitz <ogerl...@mellanox.com> Date: Wed, 23 May 2018 19:24:48 +0300
> When dealing with ingress rule on a netdev, if we did fine through the > conventional path, there's no need to continue into the egdev route, > and we can stop right there. > > Not doing so may cause a 2nd rule to be added by the cls api layer > with the ingress being the egdev. > > For example, under sriov switchdev scheme, a user rule of VFR A --> VFR B > will end up with two HW rules (1) VF A --> VF B and (2) uplink --> VF B > > Fixes: 208c0f4b5237 ('net: sched: use tc_setup_cb_call to call per-block > callbacks') > Signed-off-by: Or Gerlitz <ogerl...@mellanox.com> Applied and queued up for -stable. > As I wrote in [1], we are asking this patch to go into net and > stable >= 4.15 but not carried into net-next. Please send me a revert with a detailed commit message when this gets merged into net-next. Thanks.