From: Daniel Borkmann <daniel@iogearbox.net>
To: Cong Wang <xiyou.wangcong@gmail.com>, netdev@vger.kernel.org
Cc: Martin Olsson <martin.olsson+netdev@sentorsecurity.com>,
Jamal Hadi Salim <jhs@mojatatu.com>,
Jiri Pirko <jiri@resnulli.us>
Subject: Re: [Patch net] net_sched: refetch skb protocol for each filter
Date: Mon, 14 Jan 2019 10:23:15 +0100 [thread overview]
Message-ID: <ad311aeb-38db-f207-37fa-390c2ae1fa6e@iogearbox.net> (raw)
In-Reply-To: <20190112025542.397-1-xiyou.wangcong@gmail.com>
On 01/12/2019 03:55 AM, Cong Wang wrote:
> Martin reported a set of filters don't work after changing
> from reclassify to continue. Looking into the code, it
> looks like skb protocol is not always fetched for each
> iteration of the filters. But, as demonstrated by Martin,
> TC actions could modify skb->protocol, for example act_vlan,
> this means we have to refetch skb protocol in each iteration,
> rather than using the one we fetch in the beginning of the loop.
>
> This bug is _not_ introduced by commit 3b3ae880266d
> ("net: sched: consolidate tc_classify{,_compat}"), technically,
> if act_vlan is the only action that modifies skb protocol, then
> it is commit c7e2b9689ef8 ("sched: introduce vlan action") which
> introduced this bug.
>
> Reported-by: Martin Olsson <martin.olsson+netdev@sentorsecurity.com>
> Cc: Jamal Hadi Salim <jhs@mojatatu.com>
> Cc: Jiri Pirko <jiri@resnulli.us>
> Signed-off-by: Cong Wang <xiyou.wangcong@gmail.com>
> ---
> net/sched/cls_api.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/net/sched/cls_api.c b/net/sched/cls_api.c
> index 8ce2a0507970..e2b5cb2eb34e 100644
> --- a/net/sched/cls_api.c
> +++ b/net/sched/cls_api.c
> @@ -1277,7 +1277,6 @@ EXPORT_SYMBOL(tcf_block_cb_unregister);
> int tcf_classify(struct sk_buff *skb, const struct tcf_proto *tp,
> struct tcf_result *res, bool compat_mode)
> {
> - __be16 protocol = tc_skb_protocol(skb);
> #ifdef CONFIG_NET_CLS_ACT
> const int max_reclassify_loop = 4;
> const struct tcf_proto *orig_tp = tp;
> @@ -1287,6 +1286,7 @@ int tcf_classify(struct sk_buff *skb, const struct tcf_proto *tp,
> reclassify:
> #endif
> for (; tp; tp = rcu_dereference_bh(tp->next)) {
> + __be16 protocol = tc_skb_protocol(skb);
> int err;
>
> if (tp->protocol != protocol &&
Can't we do something like the below instead? Otherwise we'll needlessly refetch
protocol every time there is a mismatch in above tp->protocol check as well.
diff --git a/net/sched/cls_api.c b/net/sched/cls_api.c
index 8ce2a05..dc725a1 100644
--- a/net/sched/cls_api.c
+++ b/net/sched/cls_api.c
@@ -1305,6 +1305,11 @@ int tcf_classify(struct sk_buff *skb, const struct tcf_proto *tp,
#endif
if (err >= 0)
return err;
+
+ /* We also need to refetch protocol from here as e.g.
+ * act_vlan could have changed it.
+ */
+ protocol = tc_skb_protocol(skb);
}
return TC_ACT_UNSPEC; /* signal: continue lookup */
Thanks,
Daniel
next prev parent reply other threads:[~2019-01-14 9:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-12 2:55 [Patch net] net_sched: refetch skb protocol for each filter Cong Wang
2019-01-12 12:23 ` Jamal Hadi Salim
2019-01-12 15:41 ` Jamal Hadi Salim
2019-01-13 21:08 ` Cong Wang
2019-01-15 15:59 ` Jamal Hadi Salim
2019-01-15 16:21 ` Jamal Hadi Salim
2019-01-15 17:57 ` Cong Wang
2019-01-16 14:02 ` Jamal Hadi Salim
2019-01-15 17:52 ` Cong Wang
2019-01-13 20:58 ` Cong Wang
2019-01-15 15:14 ` Jamal Hadi Salim
2019-01-14 9:15 ` Martin Olsson
2019-01-15 15:19 ` Jamal Hadi Salim
2019-01-14 23:13 ` Lucas Bates
2019-01-14 9:23 ` Daniel Borkmann [this message]
2019-01-14 19:55 ` Cong Wang
2019-01-16 13:59 ` Jamal Hadi Salim
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ad311aeb-38db-f207-37fa-390c2ae1fa6e@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=martin.olsson+netdev@sentorsecurity.com \
--cc=netdev@vger.kernel.org \
--cc=xiyou.wangcong@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).