All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: mike.rapoport@ravellosystems.com
Cc: dlstevens@us.ibm.com, netdev@vger.kernel.org
Subject: Re: [PATCH net] net: vxlan: fix crash when interface is created with no group
Date: Wed, 19 Mar 2014 18:29:00 -0400 (EDT)	[thread overview]
Message-ID: <20140319.182900.467525569537111207.davem@davemloft.net> (raw)
In-Reply-To: <CAF1J0HPT3u05uu6uLYDDu7cV11Ku6AHVooSLLAoaYj6wVtfemA@mail.gmail.com>

From: Mike Rapoport <mike.rapoport@ravellosystems.com>
Date: Wed, 19 Mar 2014 21:52:31 +0200

> On Wed, Mar 19, 2014 at 9:46 PM, David Miller <davem@davemloft.net> wrote:
>> From: Mike Rapoport <mike.rapoport@ravellosystems.com>
>> Date: Wed, 19 Mar 2014 09:14:46 +0200
>>
>>> On Tue, Mar 18, 2014 at 10:55:16AM -0600, David Stevens wrote:
>>>>
>>>> Wouldn't it be better to:
>>>>
>>>> 1) make sure all of vxlan_dev is initialized before use,
>>>> especially default_dst
>>>> 2) change the v6 code to check for AF_INET6 too, and do
>>>> nothing if not set. If not set by the admin, the family of
>>>> default_dst would then be AF_UNSPEC and not match.
>>>
>>> The family of default dst is implicitly initailized to AF_UNSPEC because
>>> if kzalloc :)
>>>
>>> I agree that explicit check for AF_INET6 is much better than fallthrough
>>> with simple 'else' clause and I can send a patch that makes the checks
>>> for IPv6 as well as default_dst initialization explicit
>>>
>>> However, for the particular case in vxlan_rcv, checking the packet
>>> version seems to me semantically more correct than comparing default_dst
>>> protocol family with AF_INET or AF_INET6.
>>
>> The way I read things, we would receive packets unconditionally in the
>> pre-ipv6-support code.  So we have to keep doing so.
>>
>> Therefore we either have to check the SKB protocol or pass an explicit
>> protocol as an argument to vs->rcv(...).
> 
> Well, the patch I've sent checks for ip_hdr(skb) protocol version...

Yes, I know.

I'm just going to wait and see if anyone else in this thread
has anything more to say.

  reply	other threads:[~2014-03-19 22:29 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 [this message]
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
2014-03-29  8:29           ` Mike Rapoport
2014-03-31 20:18             ` David Miller
2014-03-24  5:09       ` Pravin Shelar
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=20140319.182900.467525569537111207.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=dlstevens@us.ibm.com \
    --cc=mike.rapoport@ravellosystems.com \
    --cc=netdev@vger.kernel.org \
    /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.