Hide Forgot
Created attachment 484381 [details] dmesg output Description of problem: Bridge module wont load conflicts with ipv6 see http://www.spinics.net/lists/netdev/msg157811.html for details.. Version-Release number of selected component (if applicable): 2.6.38-1.fc15.x86_64 How reproducible: Always Steps to Reproduce: 1. modprobe bridge 2. 3. Actual results: FATAL: Error inserting bridge (/lib/modules/2.6.38-1.fc15.x86_64/kernel/net/bridge/bridge.ko): Unknown symbol in module, or unknown parameter (see dmesg) bridge: Unknown symbol ipv6_dev_get_saddr (err 0) Expected results: Bridge module to load and pony's dropping from the sky Additional info:
Do you have ipv6 disabled?
(In reply to comment #1) > Do you have ipv6 disabled? I don't, though I've only looked in /etc/sysconfig/network. Yet the interfaces have no ipv6 addresses. Same problem for me, so thought I'd chime in.
[root@elm ~]# modinfo bridge filename: /lib/modules/2.6.38-1.xendom0.fc15.i686.PAE/kernel/net/bridge/bridge.ko version: 2.3 license: GPL srcversion: 0233A9FD6927957F911D5B0 depends: stp,llc,ipv6 vermagic: 2.6.38-1.xendom0.fc15.i686.PAE SMP mod_unload 686 [root@elm ~]# more /etc/modprobe.d/blacklist-ipv6.conf install ipv6 /bin/true blacklist ipv6 Correcting myself, yes I have ipv6 disabled. :) It's not part of an rpm, so I guess I did that on my own at some point? Does bridge really require ipv6??
Sorry for the late responce yes I'm blacklisting ipv6 same as Jerry in Comment 3
If I un-blacklist ipv6 the issue no longer manifests itself. Seems like bridge.ko depends on ipv6.
This has been a lnog standing problem with ipv6. Certain modules need to make calls into the ipv6 code to check for the existance of ipv6 addresses, and some of the functions are sufficiently large that they can't be inlined or otherwise handled without the inclusion of the ipv6 module. The workaround for this situation is to not blacklist the ipv6 module, but rather set its disable_ipv6 module option. That way the code gets loaded, but no ipv6 functionality is registered with the kernel so user space can't accesses it. It would probably be a better solution to remove the module option and split the ipv6 module into a utilities and protocol module, so that we wouldn't need this tweak. i'll look into doing that. Until then, the above should fix your problem.
Created attachment 502367 [details] patch to break dependency of bridge on ipv6 Here you go, please confirm that this patch allows you to load the bridge module with ipv6 blacklisted. Thanks!
its been a month, any feedback?
Just close this as notabug or something there was discussion about this on the kernel mailing list + users should not be blacklisting ipv6 anymore
copy that