netdev - Re: [PATCH net] net: vxlan: fix crash when interface is created with no group

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20140319.234008.1455466461924213265.davem@davemloft.net>
Date:	Wed, 19 Mar 2014 23:40:08 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	dlstevens@...ibm.com
Cc:	mike.rapoport@...ellosystems.com, netdev@...r.kernel.org
Subject: Re: [PATCH net] net: vxlan: fix crash when interface is created
 with no group

From: David Stevens <dlstevens@...ibm.com>
Date: Wed, 19 Mar 2014 14:28:11 -0600

> 
> 
> -----David Miller <davem@...emloft.net> wrote: -----
> 
>>The way I read things, we would receive packets unconditionally in
>>the
>>pre-ipv6-support code. So we have to keep doing so.
> 
> I never tried it, but as there are IP-version-specific processing (the
> whole reason we need to check to support both), I'd expect
> that before the v6 support patch, v6-encapsulated packets would have
> been dropped, or at least mishandled. We accepted all v4 packets,
> because v4 is all that was supported.

I'm not suggesting to mix protocols, I'm suggesting that the IPV4
path continues to accept all IPV4 packets.

And we know exactly what protocol it is because the vs->rcv() caller
is going to be ipv4 or ipv6 specific code.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html