diff options
| author |   David S. Miller <davem@davemloft.net> | 2018-07-07 20:20:46 +0900 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2018-07-07 20:20:46 +0900 |
| commit | a2f1483b91470804f37ce8fc69b48e8e5635c36f (patch) | |
| tree | f5b7e5aad97f87d4d5a429662ed29d8f13cc146b /tools/testing/selftests/net/forwarding | |
| parent | devlink: fix incorrect return statement (diff) | |
| parent | vxlan: fix default fdb entry netlink notify ordering during netdev create (diff) | |
| download | linux-dev-a2f1483b91470804f37ce8fc69b48e8e5635c36f.tar.xz linux-dev-a2f1483b91470804f37ce8fc69b48e8e5635c36f.zip | |
Merge branch 'vxlan-fix-default-fdb-entry-user-space-notify-ordering-race'
Roopa Prabhu says:
====================
vxlan: fix default fdb entry user-space notify ordering/race
Problem:
In vxlan_newlink, a default fdb entry is added before register_netdev.
The default fdb creation function notifies user-space of the
fdb entry on the vxlan device which user-space does not know about yet.
(RTM_NEWNEIGH goes before RTM_NEWLINK for the same ifindex).
This series fixes the user-space netlink notification ordering issue
with the following changes:
- decouple fdb notify from fdb create.
- Move fdb notify after register_netdev.
- modify rtnl_configure_link to allow configuring a link early.
- Call rtnl_configure_link in vxlan newlink handler to notify
userspace about the newlink before fdb notify and
hence avoiding the user-space race.
====================
Fixes: afbd8bae9c79 ("vxlan: add implicit fdb entry for default destination")
Signed-off-by: Roopa Prabhu <roopa@cumulusnetworks.com>
Diffstat (limited to 'tools/testing/selftests/net/forwarding')
0 files changed, 0 insertions, 0 deletions