All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xin Long <lucien.xin@gmail.com>
To: network dev <netdev@vger.kernel.org>
Cc: Steffen Klassert <steffen.klassert@secunet.com>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	"David S. Miller" <davem@davemloft.net>,
	Sabrina Dubroca <sd@queasysnail.net>
Subject: Re: [PATCH ipsec] esp4: support ipv6 nexthdrs process for beet gso segment
Date: Sun, 19 Apr 2020 15:27:42 +0800	[thread overview]
Message-ID: <CADvbK_cPp9Md06wXG19fF2jxFr7v07rnCNa5tmXGHOjNM9Ew1g@mail.gmail.com> (raw)
In-Reply-To: <b1b39c63ff48deca9e7c8011d747dcf4db05a6c1.1586509678.git.lucien.xin@gmail.com>

On Fri, Apr 10, 2020 at 5:08 PM Xin Long <lucien.xin@gmail.com> wrote:
>
> For beet mode, when it's ipv6 inner address with nexthdrs set,
> the packet format might be:
>
>     ----------------------------------------------------
>     | outer  |     | dest |     |      |  ESP    | ESP |
>     | IP hdr | ESP | opts.| TCP | Data | Trailer | ICV |
>     ----------------------------------------------------
>
> Before doing gso segment in xfrm4_beet_gso_segment(), the same
> thing is needed as it does in xfrm6_beet_gso_segment() in last
> patch 'esp6: support ipv6 nexthdrs process for beet gso segment'.
>
> Fixes: 384a46ea7bdc ("esp4: add gso_segment for esp4 beet mode")
> Signed-off-by: Xin Long <lucien.xin@gmail.com>
> ---
>  net/ipv4/esp4_offload.c | 14 ++++++++++----
>  1 file changed, 10 insertions(+), 4 deletions(-)
>
> diff --git a/net/ipv4/esp4_offload.c b/net/ipv4/esp4_offload.c
> index 731022c..9dde4e3 100644
> --- a/net/ipv4/esp4_offload.c
> +++ b/net/ipv4/esp4_offload.c
> @@ -139,7 +139,7 @@ static struct sk_buff *xfrm4_beet_gso_segment(struct xfrm_state *x,
>         struct xfrm_offload *xo = xfrm_offload(skb);
>         struct sk_buff *segs = ERR_PTR(-EINVAL);
>         const struct net_offload *ops;
> -       int proto = xo->proto;
> +       u8 proto = xo->proto;
>
>         skb->transport_header += x->props.header_len;
>
> @@ -148,10 +148,16 @@ static struct sk_buff *xfrm4_beet_gso_segment(struct xfrm_state *x,
>
>                 skb->transport_header += ph->hdrlen * 8;
>                 proto = ph->nexthdr;
> -       } else if (x->sel.family != AF_INET6) {
> +       } else if (x->sel.family == AF_INET6) {
> +               int offset = skb_transport_offset(skb);
> +               __be16 frag;
> +
> +               offset = ipv6_skip_exthdr(skb, offset, &proto, &frag);
> +               skb->transport_header += offset;
And this one too.

> +               if (proto == IPPROTO_TCP)
> +                       skb_shinfo(skb)->gso_type |= SKB_GSO_TCPV4;
> +       } else {
>                 skb->transport_header -= IPV4_BEET_PHMAXLEN;
> -       } else if (proto == IPPROTO_TCP) {
> -               skb_shinfo(skb)->gso_type |= SKB_GSO_TCPV4;
>         }
>
>         __skb_pull(skb, skb_transport_offset(skb));
> --
> 2.1.0
>

      reply	other threads:[~2020-04-19  7:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-10  9:07 [PATCH ipsec] esp4: support ipv6 nexthdrs process for beet gso segment Xin Long
2020-04-19  7:27 ` Xin Long [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=CADvbK_cPp9Md06wXG19fF2jxFr7v07rnCNa5tmXGHOjNM9Ew1g@mail.gmail.com \
    --to=lucien.xin@gmail.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=netdev@vger.kernel.org \
    --cc=sd@queasysnail.net \
    --cc=steffen.klassert@secunet.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 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.