These patches fix the Bonding module's requirement to have the IPv6
module loaded and configured by creating a new "disable" module parameter
value for ipv6.ko. This allows users who do not want any IPv6 addresses
or sockets to be created to disable IPv6 support, while still loading
the module and making it's symbols available. This can be specified in
/etc/modprobe.conf (or similar) with "options ipv6 disable=1".
I've verified that Bonding, SCTP, Sunrpc and DCCP will still load, however
dccp_ipv6 will not load when disable=1 - I believe this is ok as
IPv6 won't work anyways.
Documentation/networking/ipv6.txt | 35 +++++++++++++++++++++++++++++++++++
net/ipv6/af_inet6.c | 22 ++++++++++++++++------
net/sctp/protocol.c | 11 ++++++++---
3 files changed, 59 insertions(+), 9 deletions(-)
On 4 марта 2009 05:37:10 Brian Haley wrote:
> These patches fix the Bonding module's requirement to have the IPv6
> module loaded and configured by creating a new "disable" module
> parameter value for ipv6.ko. This allows users who do not want any
> IPv6 addresses or sockets to be created to disable IPv6 support,
> while still loading the module and making it's symbols available.
> This can be specified in /etc/modprobe.conf (or similar) with
> "options ipv6 disable=1".
>
While this is definitely the right approach, it requires completely new
infrastructure to disable IPv6 (including resolving update issues). So I
guess this is post-2.6.29 material.
From: Andrey Borzenkov <[email protected]>
Date: Wed, 4 Mar 2009 07:20:30 +0300
> On 4 марта 2009 05:37:10 Brian Haley wrote:
> > These patches fix the Bonding module's requirement to have the IPv6
> > module loaded and configured by creating a new "disable" module
> > parameter value for ipv6.ko. This allows users who do not want any
> > IPv6 addresses or sockets to be created to disable IPv6 support,
> > while still loading the module and making it's symbols available.
> > This can be specified in /etc/modprobe.conf (or similar) with
> > "options ipv6 disable=1".
>
> While this is definitely the right approach, it requires completely new
> infrastructure to disable IPv6 (including resolving update issues). So I
> guess this is post-2.6.29 material.
No, Brian's patches are is the only reasonable way to fix this
bug, even in 2.6.29
We not going to let the ipv6 module load disable hack live any
longer, sorry.
I'm going to apply and push out Brian's patches.
????{.n?+???????+%?????ݶ??w??{.n?+????{??G?????{ay? ʇڙ?,j??f???h?????????z_??(?階?ݢj"???m??????G????????????&???~???iO???z??v?^?m???? ????????I?