From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757977Ab1FFUXZ (ORCPT ); Mon, 6 Jun 2011 16:23:25 -0400 Received: from mail-ww0-f44.google.com ([74.125.82.44]:63735 "EHLO mail-ww0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756146Ab1FFUXW (ORCPT ); Mon, 6 Jun 2011 16:23:22 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:cc:in-reply-to:references:content-type:date :message-id:mime-version:x-mailer:content-transfer-encoding; b=eqtp4tTQjRd9/DnJtztStpp+Y5LjVI7Po7l2rr13PB6jVCY2ogc9wBawWJ23t6mhgi qZJwSTT27LkBlMk5zhEBVP8SIN88KQM6bx2Zbsy58W1XI4Kqdpp6wMvXyn/03LwT4Cjz gt69spdPBV6NULHtvix4iQc6PSlyu0DQNcQ6U= Subject: Re: KVM induced panic on 2.6.38[2367] & 2.6.39 From: Eric Dumazet To: Bart De Schuymer Cc: Brad Campbell , kvm@vger.kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, netfilter-devel@vger.kernel.org In-Reply-To: <4DED344D.7000005@pandora.be> 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> Content-Type: text/plain; charset="UTF-8" Date: Mon, 06 Jun 2011 22:23:17 +0200 Message-ID: <1307391797.2642.12.camel@edumazet-laptop> Mime-Version: 1.0 X-Mailer: Evolution 2.32.2 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Le lundi 06 juin 2011 à 22:10 +0200, Bart De Schuymer a écrit : > 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...)? > Keep netdev, as this most probably is a networking bug. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Dumazet Subject: Re: KVM induced panic on 2.6.38[2367] & 2.6.39 Date: Mon, 06 Jun 2011 22:23:17 +0200 Message-ID: <1307391797.2642.12.camel@edumazet-laptop> 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> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Cc: Brad Campbell , kvm@vger.kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, netfilter-devel@vger.kernel.org To: Bart De Schuymer Return-path: In-Reply-To: <4DED344D.7000005@pandora.be> Sender: owner-linux-mm@kvack.org List-Id: netdev.vger.kernel.org Le lundi 06 juin 2011 =C3=A0 22:10 +0200, Bart De Schuymer a =C3=A9crit : > Hi Brad, >=20 > This has probably nothing to do with ebtables, so please rmmod in case=20 > it's loaded. > A few questions I didn't directly see an answer to in the threads I=20 > scanned... > I'm assuming you actually use the bridging firewall functionality. So,=20 > what iptables modules do you use? Can you reduce your iptables rules to= =20 > 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=20 > require specialized hardware (I'm catching up on qemu/kvm...)? >=20 Keep netdev, as this most probably is a networking bug. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter= .ca/ Don't email: email@kvack.org From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail203.messagelabs.com (mail203.messagelabs.com [216.82.254.243]) by kanga.kvack.org (Postfix) with ESMTP id 1F1B26B007B for ; Mon, 6 Jun 2011 16:23:23 -0400 (EDT) Received: by wwi36 with SMTP id 36so3528891wwi.26 for ; Mon, 06 Jun 2011 13:23:20 -0700 (PDT) Subject: Re: KVM induced panic on 2.6.38[2367] & 2.6.39 From: Eric Dumazet In-Reply-To: <4DED344D.7000005@pandora.be> 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> Content-Type: text/plain; charset="UTF-8" Date: Mon, 06 Jun 2011 22:23:17 +0200 Message-ID: <1307391797.2642.12.camel@edumazet-laptop> Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: owner-linux-mm@kvack.org List-ID: To: Bart De Schuymer Cc: Brad Campbell , kvm@vger.kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, netfilter-devel@vger.kernel.org Le lundi 06 juin 2011 A 22:10 +0200, Bart De Schuymer a A(C)crit : > 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...)? > Keep netdev, as this most probably is a networking bug. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: email@kvack.org