[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1527092688-27496-1-git-send-email-ogerlitz@mellanox.com>
Date: Wed, 23 May 2018 19:24:48 +0300
From: Or Gerlitz <ogerlitz@...lanox.com>
To: "David S. Miller" <davem@...emloft.net>
Cc: Jiri Pirko <jiri@...lanox.com>,
Jakub Kicinski <jakub.kicinski@...ronome.com>,
Paul Blakey <paulb@...lanox.com>, netdev@...r.kernel.org,
ASAP_Direct_Dev@...lanox.com, Or Gerlitz <ogerlitz@...lanox.com>
Subject: [PATCH net] net : sched: cls_api: deal with egdev path only if needed
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 <ogerlitz@...lanox.com>
---
Hi Dave,
As I wrote in [1], we are asking this patch to go into net and
stable >= 4.15 but not carried into net-next.
thanks,
Or.
[1] https://marc.info/?l=linux-netdev&m=152660659631964&w=2
net/sched/cls_api.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net/sched/cls_api.c b/net/sched/cls_api.c
index 963e4bf..a57e112 100644
--- a/net/sched/cls_api.c
+++ b/net/sched/cls_api.c
@@ -1588,7 +1588,7 @@ int tc_setup_cb_call(struct tcf_block *block, struct tcf_exts *exts,
return ret;
ok_count = ret;
- if (!exts)
+ if (!exts || ok_count)
return ok_count;
ret = tc_exts_setup_cb_egdev_call(exts, type, type_data, err_stop);
if (ret < 0)
--
2.5.5
Powered by blists - more mailing lists