From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Jon Maxwell <jmaxwell37@gmail.com>, stephen@networkplumber.org
Cc: vyasevic@redhat.com, jpirko@redhat.com, netdev@vger.kernel.org,
jmaxwell@redhat.com, bridge@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, davem@davemloft.net
Subject: Re: [Bridge] [PATCH net] bridge: notify user space after fdb update
Date: Wed, 28 May 2014 18:19:53 +0400 [thread overview]
Message-ID: <5385F089.9080608@cogentembedded.com> (raw)
In-Reply-To: <1401230749-19507-1-git-send-email-jmaxwell37@gmail.com>
Hello.
On 05/28/2014 02:45 AM, Jon Maxwell 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>
> ---
> net/bridge/br_fdb.c | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
> diff --git a/net/bridge/br_fdb.c b/net/bridge/br_fdb.c
> index 9203d5a..f3ee2da 100644
> --- a/net/bridge/br_fdb.c
> +++ b/net/bridge/br_fdb.c
> @@ -487,6 +487,7 @@ void br_fdb_update(struct net_bridge *br, struct net_bridge_port *source,
> {
> struct hlist_head *head = &br->hash[br_mac_hash(addr, vid)];
> struct net_bridge_fdb_entry *fdb;
> + bool fdb_modified = 0;
s/0/false/.
>
> /* some users want to always flood. */
> if (hold_time(br) == 0)
> @@ -507,10 +508,15 @@ void br_fdb_update(struct net_bridge *br, struct net_bridge_port *source,
> source->dev->name);
> } else {
> /* fastpath: update of existing entry */
> - fdb->dst = source;
> + if (unlikely(source != fdb->dst)) {
> + fdb->dst = source;
> + fdb_modified = 1;
s/1/true/.
> + }
> fdb->updated = jiffies;
> if (unlikely(added_by_user))
> fdb->added_by_user = 1;
> + if (unlikely(fdb_modified))
> + fdb_notify(br, fdb, RTM_NEWNEIGH);
> }
> } else {
> spin_lock(&br->hash_lock);
WBR, Sergei
WARNING: multiple messages have this Message-ID (diff)
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Jon Maxwell <jmaxwell37@gmail.com>, stephen@networkplumber.org
Cc: 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: Wed, 28 May 2014 18:19:53 +0400 [thread overview]
Message-ID: <5385F089.9080608@cogentembedded.com> (raw)
In-Reply-To: <1401230749-19507-1-git-send-email-jmaxwell37@gmail.com>
Hello.
On 05/28/2014 02:45 AM, Jon Maxwell 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>
> ---
> net/bridge/br_fdb.c | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
> diff --git a/net/bridge/br_fdb.c b/net/bridge/br_fdb.c
> index 9203d5a..f3ee2da 100644
> --- a/net/bridge/br_fdb.c
> +++ b/net/bridge/br_fdb.c
> @@ -487,6 +487,7 @@ void br_fdb_update(struct net_bridge *br, struct net_bridge_port *source,
> {
> struct hlist_head *head = &br->hash[br_mac_hash(addr, vid)];
> struct net_bridge_fdb_entry *fdb;
> + bool fdb_modified = 0;
s/0/false/.
>
> /* some users want to always flood. */
> if (hold_time(br) == 0)
> @@ -507,10 +508,15 @@ void br_fdb_update(struct net_bridge *br, struct net_bridge_port *source,
> source->dev->name);
> } else {
> /* fastpath: update of existing entry */
> - fdb->dst = source;
> + if (unlikely(source != fdb->dst)) {
> + fdb->dst = source;
> + fdb_modified = 1;
s/1/true/.
> + }
> fdb->updated = jiffies;
> if (unlikely(added_by_user))
> fdb->added_by_user = 1;
> + if (unlikely(fdb_modified))
> + fdb_notify(br, fdb, RTM_NEWNEIGH);
> }
> } else {
> spin_lock(&br->hash_lock);
WBR, Sergei
WARNING: multiple messages have this Message-ID (diff)
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Jon Maxwell <jmaxwell37@gmail.com>, stephen@networkplumber.org
Cc: vyasevic@redhat.com, jpirko@redhat.com, netdev@vger.kernel.org,
jmaxwell@redhat.com, bridge@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, davem@davemloft.net
Subject: Re: [PATCH net] bridge: notify user space after fdb update
Date: Wed, 28 May 2014 18:19:53 +0400 [thread overview]
Message-ID: <5385F089.9080608@cogentembedded.com> (raw)
In-Reply-To: <1401230749-19507-1-git-send-email-jmaxwell37@gmail.com>
Hello.
On 05/28/2014 02:45 AM, Jon Maxwell 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>
> ---
> net/bridge/br_fdb.c | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
> diff --git a/net/bridge/br_fdb.c b/net/bridge/br_fdb.c
> index 9203d5a..f3ee2da 100644
> --- a/net/bridge/br_fdb.c
> +++ b/net/bridge/br_fdb.c
> @@ -487,6 +487,7 @@ void br_fdb_update(struct net_bridge *br, struct net_bridge_port *source,
> {
> struct hlist_head *head = &br->hash[br_mac_hash(addr, vid)];
> struct net_bridge_fdb_entry *fdb;
> + bool fdb_modified = 0;
s/0/false/.
>
> /* some users want to always flood. */
> if (hold_time(br) == 0)
> @@ -507,10 +508,15 @@ void br_fdb_update(struct net_bridge *br, struct net_bridge_port *source,
> source->dev->name);
> } else {
> /* fastpath: update of existing entry */
> - fdb->dst = source;
> + if (unlikely(source != fdb->dst)) {
> + fdb->dst = source;
> + fdb_modified = 1;
s/1/true/.
> + }
> fdb->updated = jiffies;
> if (unlikely(added_by_user))
> fdb->added_by_user = 1;
> + if (unlikely(fdb_modified))
> + fdb_notify(br, fdb, RTM_NEWNEIGH);
> }
> } else {
> spin_lock(&br->hash_lock);
WBR, Sergei
next prev parent reply other threads:[~2014-05-28 14:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-27 22:45 [Bridge] [PATCH net] bridge: notify user space after fdb update Jon Maxwell
2014-05-27 22:45 ` Jon Maxwell
2014-05-28 14:19 ` Sergei Shtylyov [this message]
2014-05-28 14:19 ` Sergei Shtylyov
2014-05-28 14:19 ` Sergei Shtylyov
2014-05-28 15:02 ` [Bridge] " Vlad Yasevich
2014-05-28 15:02 ` Vlad Yasevich
2014-05-28 15:02 ` Vlad Yasevich
-- strict thread matches above, loose matches on Subject: below --
2014-05-29 7:27 [Bridge] " Jon Maxwell
2014-05-29 7:55 ` Jiri Pirko
2014-05-29 9:15 ` Toshiaki Makita
2014-05-30 14:32 ` Stephen Hemminger
2014-06-02 5:15 ` David Miller
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=5385F089.9080608@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.