netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brad Campbell <brad@fnarfbargle.com>
To: Bart De Schuymer <bdschuym@pandora.be>
Cc: Patrick McHardy <kaber@trash.net>,
	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: Wed, 08 Jun 2011 08:15:11 +0800	[thread overview]
Message-ID: <4DEEBF0F.1070902@fnarfbargle.com> (raw)
In-Reply-To: <4DEE6815.7040504@pandora.be>

On 08/06/11 02:04, Bart De Schuymer wrote:

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

The issue with this is I don't have a configuration that does not crash 
the system. This only happens under the specific circumstance that 
traffic from VM A is being DNAT'd to VM B. If I disable 
CONFIG_BRIDGE_NETFILTER, or I leave out the DNAT then I can't replicate 
the problem as I don't seem to be able to get the packets to go where I 
want them to go.

Let me try and explain it a little more clearly with made up IP 
addresses to illustrate the problem.

I have VM A (1.1.1.2) and VM B (1.1.1.3) on br1 (1.1.1.1)
I have public IP on ppp0 (2.2.2.2).

VM B can talk to VM A using its host address (1.1.1.2) and there is no 
problem.

The DNAT says anything destined for PPP0 that is on port 443 and coming 
from anywhere other than PPP0 (ie inside the network) is to be DNAT'd to 
1.1.1.3.

So VM B (1.1.1.3) tries to connect to ppp0 (2.2.2.2) on port 443, and 
this is redirected to VM B on 1.1.1.2.

Only under this specific circumstance does the problem occur. I can get 
VM B (1.1.1.3) to talk directly to VM A (1.1.1.2) all day long and there 
is no problem, it's only when VM B tries to talk to ppp0 that there is 
an issue (and it happens within seconds of the initial connection).

All these tests have been performed with VM B being a Windows XP guest. 
Tonight I'll try it with a Linux guest and see if I can make it happen. 
If that works I might be able to come up with some reproducible test 
case for you. I have a desktop machine that has Intel VT extensions, so 
I'll work toward making a portable test case.

--
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-08  0:15 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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>
     [not found]               ` <20110601111841.GB3956@zip.com.au>
     [not found]                 ` <4DE62801.9080804@fnarfbargle.com>
     [not found]                   ` <20110601230342.GC3956@zip.com.au>
     [not found]                     ` <4DE8E3ED.7080004@fnarfbargle.com>
     [not found]                       ` <isavsg$3or$1@dough.gmane.org>
2011-06-03 16:07                         ` KVM induced panic on 2.6.38[2367] & 2.6.39 Brad Campbell
2011-06-06 20:10                           ` Bart De Schuymer
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 [this message]
     [not found]                       ` <4DEB3AE4.8040700@redhat.com>
     [not found]                         ` <4DEB8872.2060801@fnarfbargle.com>
2011-06-05 13:58                           ` Avi Kivity

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=4DEEBF0F.1070902@fnarfbargle.com \
    --to=brad@fnarfbargle.com \
    --cc=bdschuym@pandora.be \
    --cc=kaber@trash.net \
    --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).