From: "Nicolas de Pesloüan" <nicolas.2p.debian@free.fr>
To: Jay Vosburgh <fubar@us.ibm.com>
Cc: Brian Haley <brian.haley@hp.com>,
"J.A. Magallon" <jamagallon@ono.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
netdev@vger.kernel.org, Andrey Borzenkov <arvidjaar@mail.ru>,
bonding-devel@lists.sourceforge.net
Subject: Re: [Bonding-devel] 2.6.29 regression? Bonding tied to IPV6 in 29-rc5
Date: Tue, 17 Feb 2009 23:30:39 +0100 [thread overview]
Message-ID: <499B3A8F.7070609@free.fr> (raw)
In-Reply-To: <16929.1234904788@death.nxdomain.ibm.com>
Jay Vosburgh wrote:
> I'm not sure either of those really helps. Distro kernels are
> built with CONFIG_IPV6 (and would have the CONFIG_BONDING_IPV6_DINGUS
> enabled as well), so the common case users would have it enabled, too.
>
> Putting the ipv6 bits into a different module might not help,
> either, because the "core" bonding code would still have the call to the
> ipv6 functions. Unless there's some magic way to somehow know at
> runtime whether or not the ipv6 module is loaded, and only try to
> resolve those symbols if ipv6 is loaded. That seems complicated.
What about aliasing ipv6 to a dummy module "dummy-ipv6-for-bonding" that
only provide the required symbols and do (close to) nothing ?
Just my two cents.
Nicolas.
next prev parent reply other threads:[~2009-02-17 22:31 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
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 [this message]
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=499B3A8F.7070609@free.fr \
--to=nicolas.2p.debian@free.fr \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.