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  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]
Date:	Wed, 24 Jul 2013 16:12:55 +0800
From:	Fan Du <>
To:	Hannes Frederic Sowa <>
CC:	<>, <>,
	<>, <>,
	<>, <>
Subject: Re: [RFC PATCH net-next V2] net: split rt_genid for ipv4 and ipv6

Hallo Hannes

On 2013年07月23日 10:04, Hannes Frederic Sowa wrote:
> On Tue, Jul 23, 2013 at 09:37:00AM +0800, Fan Du wrote:
>> Current net name space has only one genid for both IPv4 and IPv6, it has below drawbacks:
>> - Add/delete an IPv4 address will invalidate all IPv6 routing table entries.
>> - Insert/remove XFRM policy will also invalidate both IPv4/IPv6 routing table entries
>>    even when the policy is only applied for one address family.
>> Thus, this patch attempt to split one genid for two to cater for IPv4 and IPv6 separately
>> in a fine granularity.
> For me the approach seems reasonable. We should double-check if this
> does not affect v4mapped af_inet6 sockets in any way. I could help to
> do the review if there is an agreement that the split is desirable.

Thank you for your attention :)

v4mapped af_inet6 address shouldn't cause problem, as long as the mapped
v4 address is routable in IPv4 stack, so add/delete IPv6 address doesn't
interfere IPv4 routing entry.

> Thanks,
>    Hannes


To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists