From: Jiri Pirko <jiri@resnulli.us>
To: Jon Maxwell <jmaxwell37@gmail.com>
Cc: stephen@networkplumber.org, davem@davemloft.net,
makita.toshiaki@lab.ntt.co.jp, vyasevic@redhat.com,
bridge@lists.linux-foundation.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, jpirko@redhat.com,
jmaxwell@redhat.com
Subject: Re: [PATCH net] bridge: notify user space after fdb update
Date: Thu, 29 May 2014 09:55:39 +0200 [thread overview]
Message-ID: <20140529075539.GD2942@minipsycho.orion> (raw)
In-Reply-To: <1401348436-5187-1-git-send-email-jmaxwell37@gmail.com>
Thu, May 29, 2014 at 09:27:16AM CEST, jmaxwell37@gmail.com wrote:
>There has been a number incidents recently where customers running KVM have
>reported that VM hosts on different Hypervisors are unreachable. Based on
>pcap traces we found that the bridge was broadcasting the ARP request out
>onto the network. However some NICs have an inbuilt switch which on occasions
>were broadcasting the VMs ARP request back through the physical NIC on the
>Hypervisor. This resulted in the bridge changing ports and incorrectly learning
>that the VMs mac address was external. As a result the ARP reply was directed
>back onto the external network and VM never updated it's ARP cache. This patch
>will notify the bridge command, after a fdb has been updated to identify such
>port toggling.
>
>Signed-off-by: Jon Maxwell <jmaxwell37@gmail.com>
Reviewed-by: Jiri Pirko <jiri@resnulli.us>
next prev parent reply other threads:[~2014-05-29 7:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-29 7:27 [PATCH net] bridge: notify user space after fdb update Jon Maxwell
2014-05-29 7:55 ` Jiri Pirko [this message]
2014-05-29 9:15 ` Toshiaki Makita
2014-05-30 14:32 ` Stephen Hemminger
2014-06-02 5:15 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2014-05-27 22:45 Jon Maxwell
2014-05-28 14:19 ` Sergei Shtylyov
2014-05-28 15:02 ` Vlad Yasevich
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=20140529075539.GD2942@minipsycho.orion \
--to=jiri@resnulli.us \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=jmaxwell37@gmail.com \
--cc=jmaxwell@redhat.com \
--cc=jpirko@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=makita.toshiaki@lab.ntt.co.jp \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=vyasevic@redhat.com \
/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).