linux-kernel - Re: 2.6.36-rc7: net/bridge causes temporary network I/O lockups [2]

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <4CBCB014.9080108@freenet.de>
Date:	Mon, 18 Oct 2010 22:37:40 +0200
From:	Patrick Ringl <patrick_@...enet.de>
To:	Herbert Xu <herbert@...dor.apana.org.au>
CC:	Patrick Ringl <patrick_@...enet.de>, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org, bridge@...ts.linux-foundation.org
Subject: Re: 2.6.36-rc7: net/bridge causes temporary network I/O lockups [2]

On 10/18/2010 06:16 PM, Herbert Xu wrote:
> On Sat, Oct 16, 2010 at 08:15:31PM +0200, Patrick Ringl wrote:
>    
>> Hi,
>>
>> okay I narrowed down the issue. I watched all function calls of the
>> 'bridge' module with the help of a small systemtap probe of mine. I
>> first traced a timespan where the issue did not occur, then one where it
>> did and composed an intersection of these two:
>>      
> I can't reproduce this problem here so I'll need your help to
> track it down.
>
> Can you see if you can relate the lock-ups to specific events
> such as a particular packet being sent through the bridge?
>    
The problem is definitely somewhere in the 2.6.34 commit regarding IGMP 
snooping (when disabling it, everything works). I have attached a 
tcpdump log of data coming through the bridge and data coming through an 
attached port (eth1). The lockups are easily spotted, since I use mtr to 
constantly ping the problematic machine, and there aren't any 
incoming/outgoing packets during the lockup.
> If we can recreate the problem on demand that that helps us to
> find the root cause.
>
> You mentioned that you took packet dumps on the system.  If you
> can show us the packets through the bridge and its ports when
> the problem occurs that would be great.
>
> Thanks,
>    
Anything else I could possibly provide? :-)

regards,
Patrick

Download attachment "dump_br0" of type "application/octet-stream" (2764 bytes)

Download attachment "dump_eth1" of type "application/octet-stream" (2806 bytes)