linux-kernel - Re: ixgbe->bonding->vlan->bridge->ebtables&iptables causes memory corruption

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: <1280220910.2827.1.camel@edumazet-laptop>
Date:	Tue, 27 Jul 2010 10:55:10 +0200
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	Gyorgy Jeney <nog.lkml@...il.com>
Cc:	netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: ixgbe->bonding->vlan->bridge->ebtables&iptables causes memory
 corruption

Le mardi 27 juillet 2010 à 09:15 +0200, Gyorgy Jeney a écrit :
> Hi,
> 
> I  have a rather interesting network setup here.  First I have a dual
> 10Gbit ixgbe ethernet card, being bonded into one link, on which we
> run a number of vlans, which are bridged with various virtual
> machines.  Now, to protect the box itself and the virtual machines I
> have a set of iptables and ebtables rules.  Whenever one of the
> virtual machines start the kernel, which is 2.6.35-rc6, will reliably
> panic.
> 
> This error needs both ebtables and iptables rules, without either one
> or the other, things seem to work quite well.
> 
> The errors and backtraces are many and long, so I attached the full
> dmes output, please say if you need more.

Seems tricky :(

Could you send  your {eb/ip}tables rules ?



--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/