From: Andrey Borzenkov <arvidjaar@mail.ru>
To: "Rafael J. Wysocki" <rjw@sisk.pl>, brian.haley@hp.com
Cc: netdev@vger.kernel.org, bonding-devel@lists.sourceforge.net,
"J.A. Magallón" <jamagallon@ono.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.29 regression? Bonding tied to IPV6 in 29-rc5
Date: Tue, 17 Feb 2009 21:17:14 +0300 [thread overview]
Message-ID: <200902172117.22671.arvidjaar@mail.ru> (raw)
In-Reply-To: <200902172001.41804.arvidjaar@mail.ru>
[-- Attachment #1: Type: text/plain, Size: 1224 bytes --]
On 17 of February 2009 20:01:38 Andrey Borzenkov wrote:
> Forward to bonding and netdev
>
> On 17 of February 2009 11:52:32 J.A. Magallón wrote:
> > Hi all...
> >
> > Don't know if this is specific for -rc5, I have jumped from 28.4 to
> > 29-rc5. In this latest kernel, I can not install 'bonding' module
> > if 'ipv6' is disabled to load via modprobe.conf:
> >
> > install ipv6 /bin/true
> >
> > Trying bonding gives this dmesg:
> >
> > bonding: Unknown symbol ndisc_build_skb
> > bonding: Unknown symbol in6_dev_finish_destroy
> > bonding: Unknown symbol ndisc_send_skb
> > bonding: Unknown symbol unregister_inet6addr_notifier
> > bonding: Unknown symbol register_inet6addr_notifier
> >
> > Commenting the line in modprobe.conf makes things smooth again.
> > We can not disable ipv6 anymore ?
>
> 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
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-02-17 18:17 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 [this message]
2009-02-17 20:08 ` [Bonding-devel] " Jay Vosburgh
2009-02-17 22:49 ` 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=200902172117.22671.arvidjaar@mail.ru \
--to=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).