mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: fubar@us.ibm.com
Cc: arvidjaar@mail.ru, rjw@sisk.pl, brian.haley@hp.com,
	netdev@vger.kernel.org, jamagallon@ono.com,
	bonding-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [Bonding-devel] 2.6.29 regression? Bonding tied to IPV6 in 29-rc5
Date: Tue, 17 Feb 2009 14:49:58 -0800 (PST)	[thread overview]
Message-ID: <20090217.144958.69599007.davem@davemloft.net> (raw)
In-Reply-To: <13225.1234901283@death.nxdomain.ibm.com>

From: Jay Vosburgh <fubar@us.ibm.com>
Date: Tue, 17 Feb 2009 12:08:03 -0800

> 	The simple answer (don't turn on CONFIG_IPV6) isn't really
> useful for the common case of distro kernels, which will generally have
> CONFIG_IPV6 enabled.

This whole "disable ipv6 module load in /etc/modules.conf" was
bound to eventually cause problems like this.

There are so many chicken-and-egg issues wrt. this it isn't
even funny, for example:

1) If we provide a sysctl which is a bitmask of protocols
   to disallow registering, we have the same problem we have
   now since ipv6 won't be able to load when the sock_register()
   fails.

2) If we add some ipv6 sysctl that says "don't do ipv6" so the
   module can load yet not automatically add link local ipv6
   addresses to interfaces and solicit for routers on the network,
   the sysctl can't be set until the module is loaded.

And this bonding stuff in particular wants to get into the
neighbour discovery state of the ipv6 module.  Therefore it's
not like we can split out a few functions into some kind
of "ipv6_helpers.ko" kernel module to eliminate the problem
either.

  reply	other threads:[~2009-02-17 22:50 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-13 22:20 Linux v2.6.29-rc5 Linus Torvalds
2009-02-17  8:52 ` Bonding tied to IPV6 in 29-rc5 J.A. Magallón
2009-02-17 17:01   ` 2.6.29 regression? " Andrey Borzenkov
2009-02-17 18:17     ` Andrey Borzenkov
2009-02-17 20:08       ` [Bonding-devel] " Jay Vosburgh
2009-02-17 22:49         ` David Miller [this message]
2009-02-17 20:10       ` Brian Haley
2009-02-17 20:56         ` Thomas Backlund
2009-02-17 21:06         ` [Bonding-devel] " Jay Vosburgh
2009-02-17 21:49           ` Brian Haley
2009-02-17 22:18             ` J.A. Magallón
2009-02-17 22:24             ` Jay Vosburgh
2009-03-04 11:46               ` Jan Engelhardt
2009-02-17 22:30           ` Nicolas de Pesloüan
2009-02-17 22:54           ` David Miller
2009-02-17 22:51         ` David Miller
2009-02-17 22:29     ` David Miller
2009-02-18  4:41       ` Valdis.Kletnieks
2009-02-18  5:29         ` David Miller
2009-02-18  5:55           ` Roland Dreier
2009-02-18 13:55           ` Theodore Tso
2009-02-18 16:24             ` Chuck Lever
2009-02-18 18:33               ` Vlad Yasevich
2009-02-18 19:57                 ` Brian Haley
2009-02-18 21:21                   ` John Dykstra
2009-02-18 21:29                     ` [Bonding-devel] " Stephen Hemminger
2009-02-19 13:32                   ` Herbert Xu
2009-02-18 22:14                 ` David Miller
2009-02-19  1:11                   ` Vlad Yasevich
2009-02-19 13:29             ` Herbert Xu
2009-02-18  6:55         ` Frank Blaschka
2009-02-19 18:15     ` Randy Dunlap
2009-02-19 18:19       ` Andrey Borzenkov
2009-02-19 18:20       ` Jay Vosburgh
2009-03-04  6:05   ` Jan Engelhardt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090217.144958.69599007.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=arvidjaar@mail.ru \
    --cc=bonding-devel@lists.sourceforge.net \
    --cc=brian.haley@hp.com \
    --cc=fubar@us.ibm.com \
    --cc=jamagallon@ono.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome