From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: daniel.turull@gmail.com, netdev@vger.kernel.org, voravit@kth.se,
robert@herjulf.net
Subject: Re: [PATH] dev: reusing unregistered ifindex values in net_device
Date: Thu, 18 Nov 2010 08:01:39 -0800 (PST) [thread overview]
Message-ID: <20101118.080139.193717791.davem@davemloft.net> (raw)
In-Reply-To: <1290094628.2781.195.camel@edumazet-laptop>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Thu, 18 Nov 2010 16:37:08 +0100
> Two bugs
>
> 1) ifindex is not initialized : you'll be suprised of random values
>
> 2) ifindex should not be reused. You'll be surprised so applications can
> break. SNMP comes to mind.
Right, the current algorithm is intentionally trying to avoid new
devices from using indexes that were used by another device in the
past.
next prev parent reply other threads:[~2010-11-18 16:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-18 15:25 [PATH] dev: reusing unregistered ifindex values in net_device Daniel Turull
2010-11-18 15:37 ` Eric Dumazet
2010-11-18 15:43 ` Daniel Turull
2010-11-18 16:01 ` David Miller [this message]
2010-11-18 16:14 ` Stephen Hemminger
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=20101118.080139.193717791.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=daniel.turull@gmail.com \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=robert@herjulf.net \
--cc=voravit@kth.se \
/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).