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
| ||
|
Date: Wed, 04 Mar 2009 03:11:56 -0800 (PST) From: David Miller <davem@...emloft.net> To: arvidjaar@...il.com Cc: brian.haley@...com, vladislav.yasevich@...com, chuck.lever@...cle.com, tytso@....edu, Valdis.Kletnieks@...edu, rjw@...k.pl, netdev@...r.kernel.org, bonding-devel@...ts.sourceforge.net, jamagallon@....com, linux-kernel@...r.kernel.org, fubar@...ibm.com Subject: Re: [PATCH 0/2] Bonding: fix IPv6 module requirement regression From: Andrey Borzenkov <arvidjaar@...il.com> 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.
Powered by blists - more mailing lists