From: David Miller <davem@davemloft.net>
To: willemdebruijn.kernel@gmail.com
Cc: netdev@vger.kernel.org, willemb@google.com
Subject: Re: [PATCH net-next] gso: validate gso_type on ipip style tunnels
Date: Wed, 20 Feb 2019 11:25:01 -0800 (PST) [thread overview]
Message-ID: <20190220.112501.238057192324769522.davem@davemloft.net> (raw)
In-Reply-To: <20190220155212.47248-1-willemdebruijn.kernel@gmail.com>
From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Date: Wed, 20 Feb 2019 10:52:12 -0500
> From: Willem de Bruijn <willemb@google.com>
>
> Commit 121d57af308d ("gso: validate gso_type in GSO handlers") added
> gso_type validation to existing gso_segment callback functions, to
> filter out illegal and potentially dangerous SKB_GSO_DODGY packets.
>
> Convert tunnels that now call inet_gso_segment and ipv6_gso_segment
> directly to have their own callbacks and extend validation to these.
>
> Signed-off-by: Willem de Bruijn <willemb@google.com>
Looks good, applied, thanks Willem.
prev parent reply other threads:[~2019-02-20 19:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 15:52 [PATCH net-next] gso: validate gso_type on ipip style tunnels Willem de Bruijn
2019-02-20 19:25 ` David Miller [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=20190220.112501.238057192324769522.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=willemb@google.com \
--cc=willemdebruijn.kernel@gmail.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).