Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932149Ab1FGSEL (ORCPT ); Tue, 7 Jun 2011 14:04:11 -0400 Received: from brigitte.telenet-ops.be ([195.130.137.66]:56418 "EHLO brigitte.telenet-ops.be" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753641Ab1FGSEJ (ORCPT ); Tue, 7 Jun 2011 14:04:09 -0400 Message-ID: <4DEE6815.7040504@pandora.be> Date: Tue, 07 Jun 2011 20:04:05 +0200 From: Bart De Schuymer User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; nl; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 MIME-Version: 1.0 To: Brad Campbell CC: Patrick McHardy , kvm@vger.kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, netfilter-devel@vger.kernel.org Subject: Re: KVM induced panic on 2.6.38[2367] & 2.6.39 References: <20110601011527.GN19505@random.random> <4DE5DCA8.7070704@fnarfbargle.com> <4DE5E29E.7080009@redhat.com> <4DE60669.9050606@fnarfbargle.com> <4DE60918.3010008@redhat.com> <4DE60940.1070107@redhat.com> <4DE61A2B.7000008@fnarfbargle.com> <20110601111841.GB3956@zip.com.au> <4DE62801.9080804@fnarfbargle.com> <20110601230342.GC3956@zip.com.au> <4DE8E3ED.7080004@fnarfbargle.com> <4DE906C0.6060901@fnarfbargle.com> <4DED344D.7000005@pandora.be> <4DED9C23.2030408@fnarfbargle.com> <4DEE27DE.7060004@trash.net> <4DEE3859.6070808@fnarfbargle.com> In-Reply-To: <4DEE3859.6070808@fnarfbargle.com> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 110607-0, 07/06/2011), Outbound message X-Antivirus-Status: Clean Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2164 Lines: 54 Op 7/06/2011 16:40, Brad Campbell schreef: > On 07/06/11 21:30, Patrick McHardy wrote: >> On 07.06.2011 05:33, Brad Campbell wrote: >>> On 07/06/11 04:10, Bart De Schuymer wrote: >>>> Hi Brad, >>>> >>>> This has probably nothing to do with ebtables, so please rmmod in case >>>> it's loaded. >>>> A few questions I didn't directly see an answer to in the threads I >>>> scanned... >>>> I'm assuming you actually use the bridging firewall functionality. So, >>>> what iptables modules do you use? Can you reduce your iptables >>>> rules to >>>> a core that triggers the bug? >>>> Or does it get triggered even with an empty set of firewall rules? >>>> Are you using a stock .35 kernel or is it patched? >>>> Is this something I can trigger on a poor guy's laptop or does it >>>> require specialized hardware (I'm catching up on qemu/kvm...)? >>> >>> Not specialised hardware as such, I've just not been able to reproduce >>> it outside of this specific operating scenario. >> >> The last similar problem we've had was related to the 32/64 bit compat >> code. Are you running 32 bit userspace on a 64 bit kernel? > > No, 32 bit Guest OS, but a completely 64 bit userspace on a 64 bit > kernel. > > Userspace is current Debian Stable. Kernel is Vanilla and qemu-kvm is > current git > If the bug is easily triggered with your guest os, then you could try to capture the traffic with wireshark (or something else) in a configuration that doesn't crash your system. Save the traffic in a pcap file. Then you can see if resending that traffic in the vulnerable configuration triggers the bug (I don't know if something in Windows exists, but tcpreplay should work for Linux). Once you have such a capture , chances are the bug is even easily reproducible by us (unless it's hardware-specific). Success isn't guaranteed, but I think it's worth a shot... cheers, Bart -- Bart De Schuymer www.artinalgorithms.be -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/