public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: wenxu@ucloud.cn
Cc: jhs@mojatatu.com, xiyou.wangcong@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH v2 net-next ] net/sched: cls_flower add CT_FLAGS_INVALID flag support
Date: Tue, 19 Jan 2021 17:03:23 -0300	[thread overview]
Message-ID: <20210119200323.GA3961@horizon.localdomain> (raw)
In-Reply-To: <1611045110-682-1-git-send-email-wenxu@ucloud.cn>

Acked-by: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>

The patch looks good to me, just some side comments below.

On Tue, Jan 19, 2021 at 04:31:50PM +0800, wenxu@ucloud.cn wrote:
> --- a/net/core/dev.c
> +++ b/net/core/dev.c
> @@ -3878,6 +3878,7 @@ int dev_loopback_xmit(struct net *net, struct sock *sk, struct sk_buff *skb)

I don't know why, but your patches often have function names here that
are not accurate. 

>  
>  	/* qdisc_skb_cb(skb)->pkt_len was already set by the caller. */
>  	qdisc_skb_cb(skb)->mru = 0;
> +	qdisc_skb_cb(skb)->post_ct = false;
>  	mini_qdisc_bstats_cpu_update(miniq, skb);
>  
>  	switch (tcf_classify(skb, miniq->filter_list, &cl_res, false)) {
> @@ -4960,6 +4961,7 @@ static __latent_entropy void net_tx_action(struct softirq_action *h)

Here as well.

>  
>  	qdisc_skb_cb(skb)->pkt_len = skb->len;
>  	qdisc_skb_cb(skb)->mru = 0;
> +	qdisc_skb_cb(skb)->post_ct = false;
>  	skb->tc_at_ingress = 1;
>  	mini_qdisc_bstats_cpu_update(miniq, skb);
>  
> diff --git a/net/core/flow_dissector.c b/net/core/flow_dissector.c
> index 2d70ded..c565c7a 100644
> --- a/net/core/flow_dissector.c
> +++ b/net/core/flow_dissector.c
> @@ -237,9 +237,8 @@ void skb_flow_dissect_meta(const struct sk_buff *skb,

Here, I would expect to see a label/function name just before the
skb_flow_dissect_ct definition. But that's
skb_flow_dissect_set_enc_addr_type. skb_flow_dissect_meta is still one
other function up.

>  void
>  skb_flow_dissect_ct(const struct sk_buff *skb,
>  		    struct flow_dissector *flow_dissector,
> -		    void *target_container,
> -		    u16 *ctinfo_map,
> -		    size_t mapsize)
> +		    void *target_container, u16 *ctinfo_map,
> +		    size_t mapsize, bool post_ct)
>  {
>  #if IS_ENABLED(CONFIG_NF_CONNTRACK)
>  	struct flow_dissector_key_ct *key;

  reply	other threads:[~2021-01-19 20:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-19  8:31 [PATCH v2 net-next ] net/sched: cls_flower add CT_FLAGS_INVALID flag support wenxu
2021-01-19 20:03 ` Marcelo Ricardo Leitner [this message]
2021-01-20 22:18 ` Cong Wang
2021-01-20 23:40   ` Marcelo Ricardo Leitner
2021-01-21  1:09     ` Cong Wang
2021-01-21  2:37       ` wenxu
2021-01-21  6:20 ` patchwork-bot+netdevbpf

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=20210119200323.GA3961@horizon.localdomain \
    --to=marcelo.leitner@gmail.com \
    --cc=jhs@mojatatu.com \
    --cc=netdev@vger.kernel.org \
    --cc=wenxu@ucloud.cn \
    --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