From: David Miller <davem@davemloft.net>
To: jbenc@redhat.com
Cc: netdev@vger.kernel.org, tgraf@suug.ch, pshelar@nicira.com
Subject: Re: [PATCH v2 net-next 0/4] tunnels: fix incorrect IPv4/v6 headers interpretation
Date: Sat, 29 Aug 2015 13:08:10 -0700 (PDT) [thread overview]
Message-ID: <20150829.130810.1498520909891590692.davem@davemloft.net> (raw)
In-Reply-To: <cover.1440787600.git.jbenc@redhat.com>
From: Jiri Benc <jbenc@redhat.com>
Date: Fri, 28 Aug 2015 20:48:18 +0200
> With tunneling, it is currently possible to get an IPv6 header and interpret
> it as an IPv4 header, or to interpret an IPv6 address as an IPv4 address
> (and vice versa). This leads to things like sending packets to incorrect
> address, IPv6 flow label being interpreted as IP packet length, etc.
>
> Fix several places where this can happen.
>
> Most of this is net-next only. The third patch affects net, too, but it
> doesn't seem there's anything in user space that sets the attribute at all
> currently, thus net-next is fine.
>
> Changelog:
> v2: fixed geneve after incorrect rebase on top of Pravin's patches
Series applied, thanks Jiri.
prev parent reply other threads:[~2015-08-29 20:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-28 18:48 [PATCH v2 net-next 0/4] tunnels: fix incorrect IPv4/v6 headers interpretation Jiri Benc
2015-08-28 18:48 ` [PATCH v2 net-next 1/4] ip_tunnels: convert the mode field of ip_tunnel_info to flags Jiri Benc
2015-08-28 22:15 ` Thomas Graf
2015-08-28 22:55 ` Pravin Shelar
2015-08-28 18:48 ` [PATCH v2 net-next 2/4] ip_tunnels: record IP version in tunnel info Jiri Benc
2015-08-28 22:24 ` Thomas Graf
2015-08-29 8:43 ` Jiri Benc
2015-08-28 22:55 ` Pravin Shelar
2015-08-28 18:48 ` [PATCH v2 net-next 3/4] fou: reject IPv6 config Jiri Benc
2015-08-28 18:48 ` [PATCH v2 net-next 4/4] vxlan: do not receive IPv4 packets on IPv6 socket Jiri Benc
2015-08-28 22:39 ` Thomas Graf
2015-08-29 8:55 ` Jiri Benc
2015-08-30 9:30 ` Thomas Graf
2015-08-29 20:08 ` 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=20150829.130810.1498520909891590692.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jbenc@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pshelar@nicira.com \
--cc=tgraf@suug.ch \
/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).