netdev - Re: Kernel panic when using bridge

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: <loom.20110408T153726-822@post.gmane.org>
Date:	Fri, 8 Apr 2011 13:49:32 +0000 (UTC)
From:	Sebastian Nickel <Sebastian.Nickel@...zner.de>
To:	netdev@...r.kernel.org
Subject: Re: Kernel panic when using bridge

Scot Doyle <lkml <at> scotdoyle.com> writes:

> 
> This kernel panic occurs when using a bridge. I would be grateful for 
> any ideas on how to correct it.
> 
> The panic was captured on two servers after three or four days of 
> minimal use, both configured as follows:
> - unpatched kernel 2.6.39-rc1 (commit 
> ecb78ab6f30106ab72a575a25b1cdfd1633b7ca2) with default .config options
> - br0 on single intel igb NIC (3 other NIC's unused)
> - br0 with ip address on distinct /27 subnet
> - br0:1 with ip address on distinct /24 subnet
> - br0:2 with ip address on distinct /24 subnet
> - no iptables rules
> - ebtables not installed
> 
> "net/bridge/br_netfilter.c" and "net/ipv4/ip_options.c" (in the current 
> 2.6.39-rc2 and in net-next-2.6) are identical to the versions used to 
> build this kernel.
> 

We have the same problems with kernel version 2.6.37.4 (unpatched). Almost same
stacktrace.

After some time there is a kernel panic.

-br0 contains a realtek NIC (8169) and some vnet devices used with KVM.

Any ideas would be great...

--
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