qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Beth Kon <eak@us.ibm.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] accidental mistyping of command line kills networking
Date: Wed, 28 Oct 2009 08:29:42 +0200	[thread overview]
Message-ID: <4AE7E4D6.1000008@redhat.com> (raw)
In-Reply-To: <4AE769A3.9080205@codemonkey.ws>

On 10/27/2009 11:44 PM, Anthony Liguori wrote:
>
> It's actually not okay.  You're creating a bridge with two tap devices 
> on the bridge that happen to be connected in qemu by a vlan.  If one 
> tap device receives a packet, qemu is going to forward that packet to 
> the other tap device, which will in turn send the packet to the bridge 
> which in turn sends it to the first tap device.
>
> Resulting in an infinite networking loop.
>

It shouldn't kill networking though.  If a guest has two nics connected 
to the same host bridge (a reasonable configuration), and then connects 
these two nics through its own bridge, it creates the same sort of 
loop.  If that kills networking, we have a guest-initiated DoS (not that 
the userspace-initiated DoS was much better).

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.

  reply	other threads:[~2009-10-28  6:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-27 19:12 [Qemu-devel] accidental mistyping of command line kills networking Beth Kon
2009-10-27 21:10 ` Beth Kon
2009-10-27 21:44   ` Anthony Liguori
2009-10-28  6:29     ` Avi Kivity [this message]
2009-10-28  8:34       ` Gleb Natapov
2009-10-28  8:55         ` Avi Kivity
2009-10-28  9:07           ` Gleb Natapov

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=4AE7E4D6.1000008@redhat.com \
    --to=avi@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=eak@us.ibm.com \
    --cc=qemu-devel@nongnu.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).