netdev - Re: [PATCH 0/4] Fix routing metrics

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20120210.031211.2297215055759518521.davem@davemloft.net>
Date:	Fri, 10 Feb 2012 03:12:11 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	steffen.klassert@...unet.com
Cc:	timo.teras@....fi, netdev@...r.kernel.org
Subject: Re: [PATCH 0/4] Fix routing metrics

From: Steffen Klassert <steffen.klassert@...unet.com>
Date: Fri, 10 Feb 2012 08:51:07 +0100

> On Fri, Feb 10, 2012 at 02:38:15AM -0500, David Miller wrote:
>> From: Steffen Klassert <steffen.klassert@...unet.com>
>> > 
>> > I fully agree with you here. But we check for the genid just in
>> > rt_init_metrics() which is invoked only on route cache entry
>> > creation. There is no check when the metrics are accessed,
>> > because the metrics on the inetpeer are valid on every access.
>> 
>> Every routing cache entry we will use after the flush will be
>> a newly created one!  All the old ones will be stop being used.
> 
> Yes, I know that. All inetpeer metrics are updated once with the
> first new routing cache entry that binds that inetpeer to the route.

And after a routing cache flush, that will be all routing cache
entries every used after that point.

So since this happens, you don't need to check the inetpeer at every
metric access.  The fact that all routing cache entries get recreated
will do it for you.

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html