netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jay Vosburgh <fubar@us.ibm.com>
To: Andrey Borzenkov <arvidjaar@mail.ru>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	brian.haley@hp.com, netdev@vger.kernel.org,
	"J.A. Magallón" <jamagallon@ono.com>,
	bonding-devel@lists.sourceforge.net,
	"Linux Kernel Mailing List" <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 12:08:03 -0800	[thread overview]
Message-ID: <13225.1234901283@death.nxdomain.ibm.com> (raw)
In-Reply-To: <200902172117.22671.arvidjaar@mail.ru>


Andrey Borzenkov <arvidjaar@mail.ru> wrote:

>> If IPv6 is disable in kernel config bonding loads. But I think it is
>> regression, it should be possible to disable IPv6 if not required.
>
>This hard dependency was apparently introduced by this commit:
>
>commit 305d552accae6afb859c493ebc7d98ca3371dae2
>Author: Brian Haley <brian.haley@hp.com>
>Date:   Tue Nov 4 17:51:14 2008 -0800
>
>    bonding: send IPv6 neighbor advertisement on failover

	I'm not really sure how to work around this.  If bonding is
compiled with CONFIG_IPV6, then the IPv6 support is compiled in, and
bonding will need the ipv6 module loaded to resolve its symbols.

	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.

	-J

---
	-Jay Vosburgh, IBM Linux Technology Center, fubar@us.ibm.com

  reply	other threads:[~2009-02-17 20:08 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <alpine.LFD.2.00.0902131413120.3179@localhost.localdomain>
     [not found] ` <20090217095232.5da06b9f@werewolf.home>
2009-02-17 17:01   ` 2.6.29 regression? Bonding tied to IPV6 in 29-rc5 Andrey Borzenkov
2009-02-17 18:17     ` Andrey Borzenkov
2009-02-17 20:08       ` Jay Vosburgh [this message]
2009-02-17 22:49         ` [Bonding-devel] " David Miller
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: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

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=13225.1234901283@death.nxdomain.ibm.com \
    --to=fubar@us.ibm.com \
    --cc=arvidjaar@mail.ru \
    --cc=bonding-devel@lists.sourceforge.net \
    --cc=brian.haley@hp.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;
as well as URLs for NNTP newsgroup(s).