From: Davide Caratti <dcaratti@redhat.com>
To: wenxu@ucloud.cn, kuba@kernel.org, marcelo.leitner@gmail.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH v3 net-next 2/2] net/sched: act_frag: add implict packet fragment support.
Date: Thu, 05 Nov 2020 12:03:55 +0100 [thread overview]
Message-ID: <b3713e6060246fd1649643fe29df8968be2fbbaa.camel@redhat.com> (raw)
In-Reply-To: <1604572893-16156-2-git-send-email-wenxu@ucloud.cn>
hello wenxu!
On Thu, 2020-11-05 at 18:41 +0800, 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.
>
> This patch add support for a xmit hook to mirred, that gets executed before
> xmiting the packet. Then, when act_ct gets loaded, it configs that hook.
> The frag xmit hook maybe reused by other modules.
>
> Signed-off-by: wenxu <wenxu@ucloud.cn>
> ---
[...]
> +
> +static int tcf_fragment(struct net *net, struct sk_buff *skb,
> + u16 mru, int (*xmit)(struct sk_buff *skb))
> +{
> + if (skb_network_offset(skb) > VLAN_ETH_HLEN) {
> + net_warn_ratelimited("L2 header too long to fragment\n");
> + goto err;
> + }
> +
> + if (skb->protocol == htons(ETH_P_IP)) {
small nit: use of skb->protocol here may lead to "ambiguous" results: a
VLAN "accelerated" packet is properly processed, while the same VLAN
packet with "non-accelerated" tag is not processed because skb->protocol
is htons(ETH_P_8021Q). Can I suggest use of skb_protocol(), that has
been introduced recently by Toke [1] ?
> + ip_do_fragment(net, skb->sk, skb, tcf_frag_xmit);
> + refdst_drop(orig_dst);
> + } else if (skb->protocol == htons(ETH_P_IPV6)) {
same here,
> + unsigned long orig_dst;
> + struct rt6_info tcf_frag_rt;
> +
> + tcf_frag_prepare_frag(skb, xmit);
> + memset(&tcf_frag_rt, 0, sizeof(tcf_frag_rt));
> + dst_init(&tcf_frag_rt.dst, &tcf_frag_dst_ops, NULL, 1,
> + DST_OBSOLETE_NONE, DST_NOCOUNT);
> + tcf_frag_rt.dst.dev = skb->dev;
> +
> + orig_dst = skb->_skb_refdst;
> + skb_dst_set_noref(skb, &tcf_frag_rt.dst);
> + IP6CB(skb)->frag_max_size = mru;
> +
> + ipv6_stub->ipv6_fragment(net, skb->sk, skb, tcf_frag_xmit);
> + refdst_drop(orig_dst);
> + } else {
> + net_warn_ratelimited("Failed fragment ->%s: eth=%04x, MRU=%d, MTU=%d.\n",
> + netdev_name(skb->dev), ntohs(skb->protocol),
> + mru, skb->dev->mtu);
and here (even though it's just a printout).
thanks!
--
davide
[1] https://lore.kernel.org/netdev/20200707110325.86731-1-toke@redhat.com/
next prev parent reply other threads:[~2020-11-05 11:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-05 10:41 [PATCH v3 net-next 1/2] net/sched: act_mirred: refactor the handle of xmit wenxu
2020-11-05 10:41 ` [PATCH v3 net-next 2/2] net/sched: act_frag: add implict packet fragment support wenxu
2020-11-05 11:03 ` Davide Caratti [this message]
2020-11-05 22:19 ` Jakub Kicinski
2020-11-06 8:56 ` 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=b3713e6060246fd1649643fe29df8968be2fbbaa.camel@redhat.com \
--to=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).