From mboxrd@z Thu Jan 1 00:00:00 1970 Message-Id: <4D81CCF80200007800036FFD@vpn.id2.novell.com> Date: Thu, 17 Mar 2011 07:57:28 +0000 From: "Jan Beulich" References: <4D80BC5B0200007800036D85@vpn.id2.novell.com> <4D80F494.6050906@hp.com> In-Reply-To: <4D80F494.6050906@hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: Re: [Bridge] build breakage due to br_multicast.c referencing ipv6_dev_get_saddr() List-Id: Linux Ethernet Bridging List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Brian Haley Cc: linus.luessing@web.de, netdev@vger.kernel.org, bridge@lists.linux-foundation.org, davem@davemloft.net >>> On 16.03.11 at 18:34, Brian Haley wrote: > On 03/16/2011 08:34 AM, Jan Beulich wrote: >> With BRIDGE=3Dy and IPV6=3Dm commit >> fe29ec41aaa51902aebd63658dfb04fe6fea8be5 ("bridge: Use IPv6 >> link-local address for multicast listener queries") causes the build to >> break. >>=20 >> Similary, even if both are =3Dm, but ipv6.ko got blacklisted (as is >> happening in various SuSE distros when disabling IPv6), there's >> a runtime problem since bridge.ko then won't load anymore due >> to the missing symbol. >=20 > Load the ipv6 module with disable=3D1, which is why I added it :) Indeed, I realized there is such an option only after I sent that mail. Nevertheless, I think it is overkill to load a huge module like this just to satisfy never actually used symbol references. In fact, just like it seems bogus to load ipv6.ko in a pure IPv4 environment, I think the opposite is also true: IPv4 support should be in a module, and it should be possible to not load it in a pure IPv6 environment. Jan