netdev - Re: ip6_rt_gc_elasticity and ip6_rt_gc_min_interval race in rt6_alloc

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <20121130.135014.1380924721756973206.davem@davemloft.net>
Date:	Fri, 30 Nov 2012 13:50:14 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	jbohac@...e.cz
Cc:	netdev@...r.kernel.org, mkubecek@...e.cz
Subject: Re: ip6_rt_gc_elasticity and ip6_rt_gc_min_interval race in
 rt6_alloc_cow() ?

From: Jiri Bohac <jbohac@...e.cz>
Date: Fri, 30 Nov 2012 19:43:36 +0100

> I believe there is a race condition in the setting of
> ip6_rt_gc_elasticity and ip6_rt_gc_min_interval. I have not seen
> happen, though:
> 
> 1) a setting made by the user via sysctl while ip6_dst_gc() is
>    running will get lost
> 
> 2) another instance of rt6_alloc_cow() may save the temporary
>    values in the saved_* variables, making those permanent.
> 
> Am I overlooking some synchronization or should I send a
> patch to fix this?

The ipv4 routing cache had the same issue, I really and sincerely
doubt this race matters in practice.
--
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