netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hasso Tepper <hasso@estpak.ee>
To: "YOSHIFUJI Hideaki / 吉藤英明" <yoshfuji@linux-ipv6.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
	aramoto@linux-ipv6.org, kozakai@linux-ipv6.org
Subject: Re: [GIT PULL] IPv6 Updates
Date: Wed, 14 Feb 2007 21:19:10 +0200	[thread overview]
Message-ID: <200702142119.11304.hasso@estpak.ee> (raw)
In-Reply-To: <20070215.023514.30908786.yoshfuji@linux-ipv6.org>

YOSHIFUJI Hideaki / 吉藤英明 wrote:
> commit bd292ad1ccbf15c72351f79d4a130dd50da81613
> Author: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
> Date:   Thu Feb 15 02:07:27 2007 +0900
> 
>     [IPV6] ADDRCONF: Register inet6_dev earlier.
>     
>     Allocate inet6_dev earlier to allow users to set up per-interface variables.
>     
>     Signed-off-by: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
> 
> diff --git a/net/ipv6/addrconf.c b/net/ipv6/addrconf.c
> index c6683ea..42b5cc5 100644
> --- a/net/ipv6/addrconf.c
> +++ b/net/ipv6/addrconf.c
> @@ -2246,6 +2246,14 @@ static int addrconf_notify(struct notifier_block *this, unsigned long event,
>  	int run_pending = 0;
>  
>  	switch(event) {
> +	case NETDEV_REGISTER:
> +		if (!idev) {
> +			idev = ipv6_add_dev(dev);
> +			if (!idev)
> +				printk(KERN_WARNING "IPv6: add_dev failed for %s\n",
> +					dev->name);
> +		}
> +		break;
>  	case NETDEV_UP:
>  	case NETDEV_CHANGE:
>  		if (event == NETDEV_UP) {
> 
> ---

Many thanks. Now if only IPv4 would be fixed in similar fashion as well.

Also, this reminds me related issue - "ADDRCONF(NETDEV_UP): <ifname>: link
is not ready" and "ADDRCONF(NETDEV_CHANGE): <ifname>: link becomes ready"
messages. While it may look informational, it's extremely annoying in
systems with hundreds and even thousands vlan interfaces.


regards,

-- 
Hasso Tepper

  parent reply	other threads:[~2007-02-14 19:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-14 17:35 [GIT PULL] IPv6 Updates YOSHIFUJI Hideaki / 吉藤英明
2007-02-14 19:12 ` Vlad Yasevich
2007-02-14 19:19 ` Hasso Tepper [this message]
2007-02-14 20:57   ` Herbert Xu
2007-02-14 21:31     ` Herbert Xu
2007-02-14 22:38       ` Hugo Santos
2007-02-21  8:06       ` David Miller
2007-02-21  8:09         ` YOSHIFUJI Hideaki / 吉藤英明
2007-02-21  7:15 ` David Miller
2007-02-21  8:03   ` YOSHIFUJI Hideaki / 吉藤英明
2007-02-21  9:29     ` David Miller

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=200702142119.11304.hasso@estpak.ee \
    --to=hasso@estpak.ee \
    --cc=aramoto@linux-ipv6.org \
    --cc=davem@davemloft.net \
    --cc=kozakai@linux-ipv6.org \
    --cc=netdev@vger.kernel.org \
    --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).