netdev - Re: [PATCH 2.6.38-rc8 build failure] net: bridge builtin vs. ipv6 modular

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] [day] [month] [year] [list]

Message-Id: <20110310.134908.226783215.davem@davemloft.net>
Date:	Thu, 10 Mar 2011 13:49:08 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	randy.dunlap@...cle.com
Cc:	netdev@....de, shemminger@...ux-foundation.org,
	netdev@...r.kernel.org
Subject: Re: [PATCH 2.6.38-rc8 build failure] net: bridge builtin vs. ipv6
 modular

From: Randy Dunlap <randy.dunlap@...cle.com>
Date: Thu, 10 Mar 2011 13:28:01 -0800

> This can be fixed in either of 2 ways.  One way is to require that the
> bridge code building depend on how the IPV6 code is built (builtin or modular);
> the other way is to handle the kconfig variations in net/bridge/br_multicast.c --
> but this loses some functionality if IPV6=m and BRIDGE=y.
> 
> I prefer the Kconfig patch over the br_multicast.c patch.
> Both patches are below for consideration.

I definitely prefer the Kconfig variant, although it's unfortunate that we
have a stateful dependency in the bridging multicast code.

IPV4 seems to let us use INADDR_ANY as the source address in the multicast
query, but IPV6 does not allow this (as per RFC 2710).

Anyways, I've applied the Kconfig patch, thanks Randy!
--
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