From: Brian Haley <brian.haley@hp.com>
To: David Miller <davem@davemloft.net>
Cc: arvidjaar@mail.ru, vladislav.yasevich@hp.com,
chuck.lever@oracle.com, tytso@mit.edu, Valdis.Kletnieks@vt.edu,
rjw@sisk.pl, netdev@vger.kernel.org,
bonding-devel@lists.sourceforge.net, jamagallon@ono.com,
linux-kernel@vger.kernel.org, fubar@us.ibm.com
Subject: Re: [PATCH] bonding: move IPv6 support into a separate kernel module
Date: Mon, 23 Feb 2009 09:25:07 -0500 [thread overview]
Message-ID: <49A2B1C3.2010904@hp.com> (raw)
In-Reply-To: <20090221.235901.244910753.davem@davemloft.net>
David Miller wrote:
> From: Brian Haley <brian.haley@hp.com>
> Date: Fri, 20 Feb 2009 19:31:29 -0500
>
>> [Possible fix for bonding IPv6 regression reported by Andrey Borzenkov,
>> tried to keep all Cc's]
>>
>> This patch moves the IPv6 bonding code into a separate kernel module
>> called bonding_ipv6 if either bonding or IPv6 are built as modules.
>> If both are built into the kernel then this is as well. Bonding_ipv6.ko
>> registers an "send_unsol_na" function pointer for the unsolicited
>> advertisement function to be called on a failover - the default action
>> is to do nothing. The notifier callbacks are now registered in this
>> module and not in the base bonding module.
>>
>> Signed-off-by: Brian Haley <brian.haley@hp.com>
>
> Thanks for taking the time to work on this Brian.
>
> I wonder if we aren't just trading one evil for another.
>
> Right now just configuring bonding will get the bonding
> module loaded and the ipv6 facilities will be visible.
>
> Now with your change, the user has to explicitly load
> the module. That's extremely user-unfriendly.
I agree, part of me just wanted to make sure it could be done, and figured it
was just a matter of time before my hand was forced, or the original commit was
reverted.
One idea is that the IPv6 notifier, addrconf_notify(), could try and load the
bonding_ipv6 module if a device with IFF_MASTER registered. I haven't
prototyped it to see if it would actually work, seemed like a hack.
-Brian
prev parent reply other threads:[~2009-02-23 14:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-21 0:31 [PATCH] bonding: move IPv6 support into a separate kernel module Brian Haley
2009-02-22 7:59 ` David Miller
2009-02-22 8:27 ` Willy Tarreau
2009-02-23 14:25 ` Brian Haley [this message]
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=49A2B1C3.2010904@hp.com \
--to=brian.haley@hp.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=arvidjaar@mail.ru \
--cc=bonding-devel@lists.sourceforge.net \
--cc=chuck.lever@oracle.com \
--cc=davem@davemloft.net \
--cc=fubar@us.ibm.com \
--cc=jamagallon@ono.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=tytso@mit.edu \
--cc=vladislav.yasevich@hp.com \
/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).