netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bart De Schuymer <bdschuym@pandora.be>
To: Brad Campbell <brad@fnarfbargle.com>
Cc: 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
Date: Mon, 06 Jun 2011 22:10:53 +0200	[thread overview]
Message-ID: <4DED344D.7000005@pandora.be> (raw)
In-Reply-To: <4DE906C0.6060901@fnarfbargle.com>

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...)?

cheers,
Bart

PS: I'm not sure if we should keep CC-ing everybody, netfilter-devel 
together with kvm should probably do fine.

Op 3/06/2011 18:07, Brad Campbell schreef:
> On 03/06/11 23:50, Bernhard Held wrote:
>> Am 03.06.2011 15:38, schrieb Brad Campbell:
>>> On 02/06/11 07:03, CaT wrote:
>>>> On Wed, Jun 01, 2011 at 07:52:33PM +0800, Brad Campbell wrote:
>>>>> Unfortunately the only interface that is mentioned by name anywhere
>>>>> in my firewall is $DMZ (which is ppp0 and not part of any bridge).
>>>>>
>>>>> All of the nat/dnat and other horrible hacks are based on IP 
>>>>> addresses.
>>>>
>>>> Damn. Not referencing the bridge interfaces at all stopped our host 
>>>> from
>>>> going down in flames when we passed it a few packets. These are two
>>>> of the oopses we got from it. Whilst the kernel here is .35 we got the
>>>> same issue from a range of kernels. Seems related.
>>>
>>> Well, I tried sending an explanatory message to netdev, netfilter &
>>> cc'd to kvm,
>>> but it appears not to have made it to kvm or netfilter, and the cc to
>>> netdev has
>>> not elicited a response. My resend to netfilter seems to have dropped
>>> into the
>>> bit bucket also.
>> Just another reference 3.5 months ago:
>> http://www.spinics.net/lists/netfilter-devel/msg17239.html
>
> <waves hands around shouting "I have a reproducible test case for this 
> and don't mind patching and crashing the machine to get it fixed">
>
> Attempted to add netfilter-devel to the cc this time.
> -- 
> To unsubscribe from this list: send the line "unsubscribe 
> netfilter-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>


-- 
Bart De Schuymer
www.artinalgorithms.be

--
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: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2011-06-06 20:10 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4DE44333.9000903@fnarfbargle.com>
     [not found] ` <20110531054729.GA16852@liondog.tnic>
     [not found]   ` <4DE4B432.1090203@fnarfbargle.com>
     [not found]     ` <20110531103808.GA6915@eferding.osrc.amd.com>
     [not found]       ` <4DE4FA2B.2050504@fnarfbargle.com>
     [not found]         ` <alpine.LSU.2.00.1105311517480.21107@sister.anvils>
     [not found]           ` <4DE589C5.8030600@fnarfbargle.com>
     [not found]             ` <20110601011527.GN19505@random.random>
     [not found]               ` <alpine.LSU.2.00.1105312120530.22808@sister.anvils>
     [not found]                 ` <4DE5DCA8.7070704@fnarfbargle.com>
     [not found]                   ` <4DE5E29E.7080009@redhat.com>
     [not found]                     ` <4DE60669.9050606@fnarfbargle.com>
     [not found]                       ` <4DE60918.3010008@redhat.com>
     [not found]                         ` <4DE60940.1070107@redhat.com>
     [not found]                           ` <4DE61A2B.7000008@fnarfbargle.com>
2011-06-01 11:09                             ` KVM induced panic on 2.6.38[2367] & 2.6.39 Avi Kivity
2011-06-01 11:18                             ` CaT
2011-06-01 11:52                               ` Brad Campbell
2011-06-01 23:03                                 ` CaT
2011-06-03 13:38                                   ` Brad Campbell
2011-06-03 15:50                                     ` Bernhard Held
2011-06-03 16:07                                       ` Brad Campbell
2011-06-06 20:10                                         ` Bart De Schuymer [this message]
2011-06-06 20:23                                           ` Eric Dumazet
2011-06-07  3:33                                           ` Brad Campbell
2011-06-07 13:30                                             ` Patrick McHardy
2011-06-07 14:40                                               ` Brad Campbell
2011-06-07 15:35                                                 ` Patrick McHardy
2011-06-07 18:31                                                   ` Eric Dumazet
2011-06-07 22:57                                                     ` Patrick McHardy
2011-06-08  0:18                                                       ` Brad Campbell
2011-06-08  3:59                                                         ` Eric Dumazet
2011-06-08 17:02                                                           ` Brad Campbell
2011-06-08 21:22                                                             ` Eric Dumazet
2011-06-10  2:52                                                             ` Simon Horman
2011-06-10 12:37                                                               ` Mark Lord
2011-06-10 16:43                                                                 ` Henrique de Moraes Holschuh
2011-06-12 15:38                                                               ` Avi Kivity
2011-06-07 23:43                                                   ` Brad Campbell
2011-06-07 18:04                                                 ` Bart De Schuymer
2011-06-08  0:15                                                   ` Brad Campbell
2011-06-05  8:14                                     ` Avi Kivity
2011-06-05 13:45                                       ` Brad Campbell
2011-06-05 13:58                                         ` Avi Kivity
2011-06-06 20:22                                         ` Eric Dumazet
2011-06-07 13:27                                           ` Brad Campbell
2011-06-07 13:37                                             ` Eric Dumazet
2011-06-07 15:15                                               ` Brad Campbell
2011-08-20 13:16                                               ` Brad Campbell
2011-08-22  6:36                                                 ` Avi Kivity
2011-08-22  6:45                                                   ` Eric Dumazet
2011-08-22 11:45                                                     ` Brad Campbell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4DED344D.7000005@pandora.be \
    --to=bdschuym@pandora.be \
    --cc=brad@fnarfbargle.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).