From: "David S. Miller" <davem@davemloft.net>
To: Jay Vosburgh <fubar@us.ibm.com>
Cc: yoshfuji@linux-ipv6.org, netdev@oss.sgi.com,
ikebe.takashi@lab.ntt.co.jp, akpm@osdl.org,
ctindel@users.sourceforge.net,
bonding-devel@lists.sourceforge.net
Subject: Re: [Bonding-devel] Re: [Bugme-new] [Bug 4189] New: IPv6 link local addresses are not assigned correctly on multiple-bonding enviromrnts
Date: Thu, 10 Feb 2005 19:44:54 -0800 [thread overview]
Message-ID: <20050210194454.015f3d98.davem@davemloft.net> (raw)
In-Reply-To: <200502110240.j1B2eTj3001689@death.nxdomain.ibm.com>
On Thu, 10 Feb 2005 18:40:29 -0800
Jay Vosburgh <fubar@us.ibm.com> wrote:
> Except that most of the bonding internal MAC changes won't
> generate any events (presuming you mean a NETDEV_CHANGEADDR). The
> bonding driver calls the slave's dev->set_mac_address directly; the
> NETDEV_CHANGEADDR is generated by dev_ifsioc() (which isn't exported).
> Now that I'm looking for it, there are some other cases of bonding
> calling other dev->functions directly, e.g., change_mtu, that have
> wrappers that generate events; I need to fix that.
>
> Would you have a problem with putting the SIOCSIFHWADDR code
> from dev_ifsioc() into a separate exported function, similarly to how
> dev_set_mtu() is done? I can probably whip that up along with the
> appropriate bonding changes this evening.
That would be a great idea, as I read your first paragraph I was
going to suggest exactly this.
next prev parent reply other threads:[~2005-02-11 3:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-10 8:23 Fw: [Bugme-new] [Bug 4189] New: IPv6 link local addresses are not assigned correctly on multiple-bonding enviromrnts Andrew Morton
2005-02-10 9:22 ` YOSHIFUJI Hideaki / 吉藤英明
2005-02-10 9:25 ` YOSHIFUJI Hideaki / 吉藤英明
2005-02-10 11:59 ` Takashi Ikebe
2005-02-10 18:17 ` [Bonding-devel] " Jay Vosburgh
2005-02-10 20:27 ` David S. Miller
2005-02-10 21:26 ` Rick Jones
2005-02-11 2:40 ` Jay Vosburgh
2005-02-11 3:44 ` David S. Miller [this message]
2005-02-10 20:25 ` David S. Miller
2005-02-11 0:29 ` YOSHIFUJI Hideaki / 吉藤英明
2005-02-11 1:06 ` David S. Miller
2005-02-11 1:40 ` Rick Jones
2005-02-11 2:17 ` YOSHIFUJI Hideaki / 吉藤英明
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=20050210194454.015f3d98.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@osdl.org \
--cc=bonding-devel@lists.sourceforge.net \
--cc=ctindel@users.sourceforge.net \
--cc=fubar@us.ibm.com \
--cc=ikebe.takashi@lab.ntt.co.jp \
--cc=netdev@oss.sgi.com \
--cc=yoshfuji@linux-ipv6.org \
/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).