All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xin Long <lucien.xin@gmail.com>
To: network dev <netdev@vger.kernel.org>,
	davem@davemloft.net, kuba@kernel.org
Cc: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>,
	Davide Caratti <dcaratti@redhat.com>,
	Hangbin Liu <liuhangbin@gmail.com>
Subject: [PATCH net 0/2] net: sched: drop ct and dst for the packets toward ingress in act_mirred
Date: Mon, 20 Sep 2021 06:19:20 -0400	[thread overview]
Message-ID: <cover.1632133123.git.lucien.xin@gmail.com> (raw)

With the old ct and dst carried on these packets mirred or redirrected
to ingress, it may cause these packets to be dropped on rx path. This
issue could be easily triggered when using OVS HWOL on OVN-k8s. To fix
it this patchset is to drop ct and dst for these packets, just as it
does in internal_dev_recv() in OVS module.

Xin Long (2):
  net: sched: drop ct for the packets toward ingress only in act_mirred
  net: sched: also drop dst for the packets toward ingress in act_mirred

 net/sched/act_mirred.c | 15 ++++++---------
 1 file changed, 6 insertions(+), 9 deletions(-)

-- 
2.27.0


             reply	other threads:[~2021-09-20 10:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-20 10:19 Xin Long [this message]
2021-09-20 10:19 ` [PATCH net 1/2] net: sched: drop ct for the packets toward ingress only in act_mirred Xin Long
2021-09-20 18:31   ` Cong Wang
2021-09-21  7:01     ` Xin Long
2021-09-22  3:43       ` Cong Wang
2021-09-22  5:17         ` Xin Long
2021-09-24 23:04           ` mleitner
2021-09-20 10:19 ` [PATCH net 2/2] net: sched: also drop dst for the packets toward ingress " Xin Long
2021-09-20 18:34   ` Cong Wang
2021-09-21  7:01     ` Xin Long
2021-09-22  3:52       ` Cong Wang
2021-09-22  5:29         ` Xin Long
2021-09-23 16:06         ` 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=cover.1632133123.git.lucien.xin@gmail.com \
    --to=lucien.xin@gmail.com \
    --cc=davem@davemloft.net \
    --cc=dcaratti@redhat.com \
    --cc=kuba@kernel.org \
    --cc=liuhangbin@gmail.com \
    --cc=marcelo.leitner@gmail.com \
    --cc=netdev@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.