From: wenxu@ucloud.cn
To: kuba@kernel.org, marcelo.leitner@gmail.com, dcaratti@redhat.com,
vladbu@nvidia.com
Cc: netdev@vger.kernel.org
Subject: [PATCH v5 net-next 0/3] net/sched: fix over mtu packet of defrag in
Date: Sun, 8 Nov 2020 07:30:25 +0800 [thread overview]
Message-ID: <1604791828-7431-1-git-send-email-wenxu@ucloud.cn> (raw)
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 | 51 ++++++++++++++
net/sched/act_ct.c | 7 ++
net/sched/act_frag.c | 164 ++++++++++++++++++++++++++++++++++++++++++++++
net/sched/act_mirred.c | 21 ++++--
9 files changed, 269 insertions(+), 11 deletions(-)
create mode 100644 net/sched/act_frag.c
--
1.8.3.1
next reply other threads:[~2020-11-07 23:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-07 23:30 wenxu [this message]
2020-11-07 23:30 ` [PATCH v5 net-next 1/3] net/sched: fix miss init the mru in qdisc_skb_cb wenxu
2020-11-07 23:30 ` [PATCH v5 net-next 2/3] net/sched: act_mirred: refactor the handle of xmit wenxu
2020-11-07 23:30 ` [PATCH v5 net-next 3/3] net/sched: act_frag: add implict packet fragment support wenxu
2020-11-09 13:24 ` Vlad Buslov
2020-11-09 14:50 ` Marcelo Ricardo Leitner
2020-11-09 15:47 ` Vlad Buslov
2020-11-09 16:44 ` Marcelo Ricardo Leitner
2020-11-09 14:54 ` wenxu
2020-11-09 15:51 ` Vlad Buslov
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=1604791828-7431-1-git-send-email-wenxu@ucloud.cn \
--to=wenxu@ucloud.cn \
--cc=dcaratti@redhat.com \
--cc=kuba@kernel.org \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=vladbu@nvidia.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).