From: David Miller <davem@davemloft.net>
To: ja@ssi.bg
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] ipv4: Cache source address in nexthop entries.
Date: Tue, 15 Mar 2011 16:02:19 -0700 (PDT) [thread overview]
Message-ID: <20110315.160219.189709250.davem@davemloft.net> (raw)
In-Reply-To: <alpine.LFD.2.00.1103151135110.1729@ja.ssi.bg>
From: Julian Anastasov <ja@ssi.bg>
Date: Tue, 15 Mar 2011 12:00:33 +0200 (EET)
> I see another problem with nh_saddr. fib_info
> is reused when NHs and some parameters are equal but the
> scope is not part of the fib_info and it is wrong to cache
> route scope in NH or even in fib_info. The problem is
> that we can expose in nh_saddr addresses with wrong
> scope for the route. It happens when two routes with
> different route scope reuse same fib_info.
>
> First thought is that the field fa_scope can be
> moved into fib_scope in struct fib_info, not to use
> nh_cfg_scope. Then fib_find_info can differentiate the
> entries by fib_scope. It means, fib_info will not be reused
> if fib_scope is different. For FIB_RES_PREFSRC I assume we
> can access fib_info from nh->nh_parent safely when
> refreshing nh_saddr.
>
> Here is a script that demonstrates the wrong
> exposing:
Thanks for all of your feedback Julian, I will look into
this very soon.
next prev parent reply other threads:[~2011-03-15 23:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 4:58 [PATCH] ipv4: Cache source address in nexthop entries David Miller
2011-03-08 9:57 ` Julian Anastasov
2011-03-08 18:38 ` David Miller
2011-03-08 19:03 ` David Miller
2011-03-15 10:00 ` Julian Anastasov
2011-03-15 23:02 ` David Miller [this message]
2011-03-09 0:49 ` Julian Anastasov
2011-03-09 21:08 ` David Miller
2011-03-09 23:32 ` Julian Anastasov
2011-03-09 23:40 ` 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=20110315.160219.189709250.davem@davemloft.net \
--to=davem@davemloft.net \
--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).