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] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 03 Oct 2012 16:01:02 +0100
From:	Chris Clayton <>
To:	David Miller <>
Subject: Re: Possible networking regression in 3.6.0

On 10/03/12 04:10, David Miller wrote:
> From: Julian Anastasov <>
> Date: Wed, 3 Oct 2012 02:24:53 +0300 (EEST)
>> 	Can it be a problem related to fib_info reuse
>> from different routes. For example, when local IP address
>> is created for subnet we have:
>> broadcast dev DEV  proto kernel  scope link  src
>> dev DEV  proto kernel  scope link  src
>> local dev DEV  proto kernel  scope host  src
>> 	The "dev DEV  proto kernel  scope link  src" is
>> a reused fib_info structure where we put cached routes.
>> The result can be same fib_info for and
>> RTN_BROADCAST is cached only for input
>> routes. Incoming broadcast to can be cached
>> and can cause problems for traffic forwarded to
>> So, this patch should solve the problem because it
>> separates the broadcast from unicast traffic.
> Now I understand the problem.
> I think the way to fix this is to add cfg->fc_type as another
> thing that fib_info objects are key'd by.
> I think it also would fix your obscure output multicast case too.

I've seen the discussion about whether Eric's patch is OK or not, but 
thought I'd give it a spin anyway. It applies to 3.6.0 with some fuzz, 
but I can confirm that with the patch applied I can now ping my router 
and browse the internet from a KVM client, so the Eric's diagnosis 
matches the problem I reported.

However, after closing the client, I got an oops. I've taken a 
photograph of the screen and uploaded it to As it's 
not the final patch, this may be a red herring, but I thought I'd better 
give a heads up anyway.

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