bridge: Handle IFLA_ADDRESS correctly when creating bridge device
authorToshiaki Makita <makita.toshiaki@lab.ntt.co.jp>
Fri, 25 Apr 2014 08:01:18 +0000 (17:01 +0900)
committerBen Hutchings <ben@decadent.org.uk>
Mon, 9 Jun 2014 12:28:58 +0000 (13:28 +0100)
commit084e4e55275849449a563b7b657c88caa97f8062
tree191cad8d0721060ef50068bc93a7d1106cf3127d
parent483e962b13e732cc5b06631a15a2387b017b3152
bridge: Handle IFLA_ADDRESS correctly when creating bridge device

[ Upstream commit 30313a3d5794472c3548d7288e306a5492030370 ]

When bridge device is created with IFLA_ADDRESS, we are not calling
br_stp_change_bridge_id(), which leads to incorrect local fdb
management and bridge id calculation, and prevents us from receiving
frames on the bridge device.

Reported-by: Tom Gundersen <teg@jklm.no>
Signed-off-by: Toshiaki Makita <makita.toshiaki@lab.ntt.co.jp>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
net/bridge/br_netlink.c