From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: Paul Blakey <paulb@nvidia.com>
Cc: dev@openvswitch.org, netdev@vger.kernel.org,
Saeed Mahameed <saeedm@nvidia.com>,
Cong Wang <xiyou.wangcong@gmail.com>,
Jamal Hadi Salim <jhs@mojatatu.com>,
Pravin B Shelar <pshelar@ovn.org>,
davem@davemloft.net, Jiri Pirko <jiri@nvidia.com>,
wenxu <wenxu@ucloud.cn>, Oz Shlomo <ozsh@nvidia.com>,
Vlad Buslov <vladbu@nvidia.com>, Roi Dayan <roid@nvidia.com>
Subject: Re: [PATCH net v2 0/3] net/sched: Fix ct zone matching for invalid conntrack state
Date: Thu, 9 Dec 2021 09:11:07 -0300 [thread overview]
Message-ID: <YbHyW501AWOUZn7c@t14s.localdomain> (raw)
In-Reply-To: <20211209075734.10199-1-paulb@nvidia.com>
On Thu, Dec 09, 2021 at 09:57:31AM +0200, Paul Blakey wrote:
> Changelog:
> 1->2:
> Cover letter wording
> Added blamed CCs
Thanks.
>
> Paul Blakey (3):
> net/sched: Extend qdisc control block with tc control block
> net/sched: flow_dissector: Fix matching on zone id for invalid conns
> net: openvswitch: Fix matching zone id for invalid conns arriving from tc
I keep getting surprised by how much metadata we have on CT other than
skb->_nfct. :-)
Reviewed-by: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
prev parent reply other threads:[~2021-12-09 12:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 7:57 [PATCH net v2 0/3] net/sched: Fix ct zone matching for invalid conntrack state Paul Blakey
2021-12-09 7:57 ` [PATCH net v2 1/3] net/sched: Extend qdisc control block with tc control block Paul Blakey
2021-12-09 7:57 ` [PATCH net v2 2/3] net/sched: flow_dissector: Fix matching on zone id for invalid conns Paul Blakey
2021-12-11 4:52 ` Jakub Kicinski
2021-12-12 0:47 ` Cong Wang
2021-12-14 17:07 ` Paul Blakey
2021-12-09 7:57 ` [PATCH net v2 3/3] net: openvswitch: Fix matching zone id for invalid conns arriving from tc Paul Blakey
2021-12-09 12:11 ` Marcelo Ricardo Leitner [this message]
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=YbHyW501AWOUZn7c@t14s.localdomain \
--to=marcelo.leitner@gmail.com \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=jhs@mojatatu.com \
--cc=jiri@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=ozsh@nvidia.com \
--cc=paulb@nvidia.com \
--cc=pshelar@ovn.org \
--cc=roid@nvidia.com \
--cc=saeedm@nvidia.com \
--cc=vladbu@nvidia.com \
--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