From: Jason Wang <jasowang@redhat.com>
To: jhs@mojatatu.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
davem@davemloft.net
Subject: Re: [PATCH] act_mirred: do not drop packets when fails to mirror it
Date: Wed, 15 Aug 2012 21:42:03 +0800 [thread overview]
Message-ID: <502BA72B.6070205@redhat.com> (raw)
In-Reply-To: <1345034141.20443.12.camel@mojatatu>
On 08/15/2012 08:35 PM, Jamal Hadi Salim wrote:
> On Wed, 2012-08-15 at 17:37 +0800, Jason Wang wrote:
>> We drop packet unconditionally when we fail to mirror it. This is not intended
>> in some cases.
> Hi Jason,
> Did you actually notice the behavior you described or were you going by
> the XXX comment I had in the code?
>
> cheers,
> jamal
Hi Jamal:
I met it actually through the following steps:
- start a kvm guest with tap and make it to be an interface of the bridge
- mirror the ingress traffic of the bridge to the tap
- terminate the qemu process, the tap device is then removed
- all packet goes to bridge would be dropped, so the network of guests
in the same bridge would be broken
It's hard for the management to forcast the termination of the porcess
and clean the mirroring before. The realistic way is to remove the
mirroring after the termination of the process. So, if we drop the
packets when the mirred device (tap) is removed, in the gap between the
qemu termitnaion and disabling mirroring, the bridge ( and other VMs
using the it) would not recevie any packet.
>
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-08-15 13:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-15 9:37 [PATCH] act_mirred: do not drop packets when fails to mirror it Jason Wang
2012-08-15 12:35 ` Jamal Hadi Salim
2012-08-15 13:42 ` Jason Wang [this message]
2012-08-15 15:10 ` Jamal Hadi Salim
2012-08-16 6:40 ` Jason Wang
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=502BA72B.6070205@redhat.com \
--to=jasowang@redhat.com \
--cc=davem@davemloft.net \
--cc=jhs@mojatatu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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).