netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: alexandre.sidorenko@hp.com
Cc: netdev@vger.kernel.org, ja@ssi.bg
Subject: Re: Stale entries in RT_TABLE_LOCAL
Date: Wed, 09 Mar 2011 13:53:08 -0800 (PST)	[thread overview]
Message-ID: <20110309.135308.102544831.davem@davemloft.net> (raw)
In-Reply-To: <201102231243.23579.alexandre.sidorenko@hp.com>

From: Alex Sidorenko <alexandre.sidorenko@hp.com>
Date: Wed, 23 Feb 2011 12:43:23 -0500

> I am not sure what is the best way to fix this, I can think of several 
> approaches:
> 
>   (a) change the sources so that it would be impossible to add the same IP 
>       multiple times, even with different masks. I cannot think of any
>       situation where adding the same IP (but with different mask) to the same
>       interface could be useful. But maybe I am wrong?

I'm leaning towards this solution if it's viable.  But I'm not so sure that
nobody uses this feature, maybe Julian knows?

Julian, the issue is that if you add the same IP address multiple times using
different subnet masks, we allow it.

But removal doesn't work correctly, we clear the IFA list on the device but we
leave stale entries in the local routing table.

The test case is:

ip addr add 192.168.142.109/23 dev dummy0
ip addr add 192.168.142.109/22 dev dummy0
ip addr del 192.168.142.109/22 dev dummy0
ip addr del 192.168.142.109/23 dev dummy0

  reply	other threads:[~2011-03-09 21:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-23 17:43 Stale entries in RT_TABLE_LOCAL Alex Sidorenko
2011-03-09 21:53 ` David Miller [this message]
2011-03-10  0:04   ` Julian Anastasov
2011-03-10  1:50     ` Julian Anastasov
2011-03-10 19:41       ` Alex Sidorenko
2011-03-15  8:47         ` Julian Anastasov
2011-03-17 16:11           ` Jiri Bohac
2011-03-18 22:57             ` Julian Anastasov

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=20110309.135308.102544831.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=alexandre.sidorenko@hp.com \
    --cc=ja@ssi.bg \
    --cc=netdev@vger.kernel.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).