netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vlad Buslov <vladbu@nvidia.com>
To: <wenxu@ucloud.cn>
Cc: <kuba@kernel.org>, <marcelo.leitner@gmail.com>,
	<dcaratti@redhat.com>, <netdev@vger.kernel.org>
Subject: Re: [PATCH v6 net-next 0/3] net/sched: fix over mtu packet of defrag in
Date: Tue, 10 Nov 2020 20:23:27 +0200	[thread overview]
Message-ID: <ygnha6vpvzog.fsf@nvidia.com> (raw)
In-Reply-To: <1604989686-8171-1-git-send-email-wenxu@ucloud.cn>


On Tue 10 Nov 2020 at 08:28, wenxu@ucloud.cn wrote:
> From: wenxu <wenxu@ucloud.cn>
>
> Currently kernel tc subsystem can do conntrack in act_ct. But when several
> fragment packets go through the act_ct, function tcf_ct_handle_fragments
> will defrag the packets to a big one. But the last action will redirect
> mirred to a device which maybe lead the reassembly big packet over the mtu
> of target device.
>
> The first patch fix miss init the qdisc_skb_cb->mru
> The send one refactor the hanle of xmit in act_mirred and prepare for the
> third one
> The last one add implict packet fragment support to fix the over mtu for
> defrag in act_ct.
>
> wenxu (3):
>   net/sched: fix miss init the mru in qdisc_skb_cb
>   net/sched: act_mirred: refactor the handle of xmit
>   net/sched: act_frag: add implict packet fragment support.
>
>  include/net/act_api.h     |  16 +++++
>  include/net/sch_generic.h |   5 --
>  net/core/dev.c            |   2 +
>  net/sched/Kconfig         |  13 ++++
>  net/sched/Makefile        |   1 +
>  net/sched/act_api.c       |  47 +++++++++++++
>  net/sched/act_ct.c        |   7 ++
>  net/sched/act_frag.c      | 164 ++++++++++++++++++++++++++++++++++++++++++++++
>  net/sched/act_mirred.c    |  21 ++++--
>  9 files changed, 265 insertions(+), 11 deletions(-)
>  create mode 100644 net/sched/act_frag.c

Hi,

I ran our CT tests with this series and kernel debug configs enabled
without any issue.

Tested-by: Vlad Buslov <vladbu@nvidia.com>

  parent reply	other threads:[~2020-11-10 18:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-10  6:28 [PATCH v6 net-next 0/3] net/sched: fix over mtu packet of defrag in wenxu
2020-11-10  6:28 ` [PATCH v6 net-next 1/3] net/sched: fix miss init the mru in qdisc_skb_cb wenxu
2020-11-10  6:28 ` [PATCH v6 net-next 2/3] net/sched: act_mirred: refactor the handle of xmit wenxu
2020-11-10  6:28 ` [PATCH v6 net-next 3/3] net/sched: act_frag: add implict packet fragment support wenxu
2020-11-11  0:16   ` Jakub Kicinski
2020-11-10 18:23 ` Vlad Buslov [this message]
2020-11-10 18:59 ` [PATCH v6 net-next 0/3] net/sched: fix over mtu packet of defrag in Marcelo Ricardo Leitner

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=ygnha6vpvzog.fsf@nvidia.com \
    --to=vladbu@nvidia.com \
    --cc=dcaratti@redhat.com \
    --cc=kuba@kernel.org \
    --cc=marcelo.leitner@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=wenxu@ucloud.cn \
    /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).