linux-kernel - Bridged networking panics

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

Message-ID: <4FEC62DD.6000303@navynet.it>
Date:	Thu, 28 Jun 2012 15:57:49 +0200
From:	Massimo Cetra <ctrix+debianbugs@...ynet.it>
To:	netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Bridged networking panics

Hi all,

i'm attaching 3 panics of a 3.2.X kernel.
The panics were obtained with a 3.2.20 from debian testing and from a 
vanilla compile of 3.2.21.

Those panics have been already posted some months ago [1] but are not fixed.

The problems seems related to bridged networking.
Whenever there is a bridged aliased interface (like br0:1 br0:2 etcc), 
the server will panic after some time. The more the network load, the 
shortest the uptime.
Removing (ifconfig br0:1 down) or adding back an interface seems to help 
the panic to appear.

Any more hints ?

MC

[1] for example http://comments.gmane.org/gmane.linux.network/226912

View attachment "3.2.20.2-1.txt" of type "text/plain" (16034 bytes)

View attachment "3.2.20.2-2.txt" of type "text/plain" (17032 bytes)

View attachment "3.2.21-1.txt" of type "text/plain" (23789 bytes)