[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20180722.105426.1606927541503763499.davem@davemloft.net>
Date: Sun, 22 Jul 2018 10:54:26 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: roopa@...ulusnetworks.com
Cc: netdev@...r.kernel.org
Subject: Re: [PATCH net 0/4] vxlan: fix default fdb entry user-space notify
ordering/race
From: Roopa Prabhu <roopa@...ulusnetworks.com>
Date: Fri, 20 Jul 2018 13:21:00 -0700
> From: Roopa Prabhu <roopa@...ulusnetworks.com>
>
> 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@...ulusnetworks.com>
Series applied and queued up for -stable, thanks Roopa.
Powered by blists - more mailing lists