From: Mike Rapoport <mike.rapoport@ravellosystems.com>
To: Cong Wang <cwang@twopensource.com>
Cc: David Stevens <dlstevens@us.ibm.com>,
David Miller <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>,
Or Gerlitz <or.gerlitz@gmail.com>
Subject: Re: [PATCH net] net: vxlan: fix crash when interface is created with no group
Date: Fri, 28 Mar 2014 12:05:56 +0300 [thread overview]
Message-ID: <20140328090556.GA9504@zed> (raw)
In-Reply-To: <CAHA+R7NY45pgO=5MjXQ_6WOW=32uMsV6vO1T2562VzezZLfUcA@mail.gmail.com>
On Thu, Mar 27, 2014 at 01:20:25PM -0700, Cong Wang wrote:
> On Wed, Mar 26, 2014 at 10:50 AM, Mike Rapoport
> <mike.rapoport@ravellosystems.com> wrote:
> >
> > The problem is not only duplication of default destinations, but also
> > the mis^Wuse of default_dst to distinguish whether IPv4 or IPv6 path
> > should be taken because there is no explicit specification of the
> > protocol if neither IFLA_VXLAN_GROUP or IFLA_VXLAN_LOCAL defined at
> > vxlan_newlink. Moreover, if neither of these attributes is present, the
> > custom configuration will always use v4 socket regardles of use of
> > default_dst or fdb entry.
>
> It should default to IPv4 for compatibility reason.
Yes, of course. The problem is that when IPv4 is not explicitly defined
using GROUP/LOCAL attributes, there are a lot of places that take IPv6
path.
So, what I'm proposing is to explicitly set default_dst family to
AF_INET and override it with AF_INET6 only when IPv6 is explicitly
requested.
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2014-03-28 9:06 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-17 11:17 [PATCH net] net: vxlan: fix crash when interface is created with no group Mike Rapoport
2014-03-17 16:34 ` Stephen Hemminger
2014-03-18 15:10 ` Or Gerlitz
2014-03-18 15:51 ` Mike Rapoport
2014-03-19 3:20 ` David Miller
2014-03-19 6:56 ` Mike Rapoport
2014-03-18 16:41 ` Cong Wang
2014-03-18 16:55 ` David Stevens
2014-03-18 18:07 ` Cong Wang
2014-03-19 7:14 ` Mike Rapoport
2014-03-19 19:46 ` David Miller
2014-03-19 19:52 ` Mike Rapoport
2014-03-19 22:29 ` David Miller
2014-03-19 20:28 ` David Stevens
2014-03-20 3:40 ` David Miller
2014-03-19 14:08 ` David Stevens
2014-03-19 14:32 ` Mike Rapoport
2014-03-19 14:40 ` David Stevens
2014-03-20 20:02 ` David Miller
2014-03-21 5:06 ` Mike Rapoport
2014-03-20 20:47 ` David Stevens
2014-03-21 10:22 ` Mike Rapoport
2014-03-21 11:22 ` David Stevens
2014-03-21 15:31 ` Mike Rapoport
2014-03-23 9:27 ` Mike Rapoport
2014-03-23 14:43 ` Or Gerlitz
2014-03-26 0:53 ` David Miller
2014-03-26 9:47 ` Mike Rapoport
2014-03-26 14:47 ` David Stevens
2014-03-26 17:50 ` Mike Rapoport
2014-03-27 20:20 ` Cong Wang
2014-03-28 9:05 ` Mike Rapoport [this message]
2014-03-29 8:29 ` Mike Rapoport
2014-03-31 20:18 ` David Miller
2014-03-24 5:09 ` Pravin Shelar
-- strict thread matches above, loose matches on Subject: below --
2014-04-01 6:23 Mike Rapoport
2014-04-01 19:22 ` Cong Wang
2014-04-02 5:51 ` Mike Rapoport
2014-04-03 15:19 ` David Miller
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=20140328090556.GA9504@zed \
--to=mike.rapoport@ravellosystems.com \
--cc=cwang@twopensource.com \
--cc=davem@davemloft.net \
--cc=dlstevens@us.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=or.gerlitz@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).