On Thu, 2013-05-02 at 19:33 -0700, Thomas Pedersen wrote: > After turning carrier off, any parent bridge interface > needs to be notified. Otherwise we would see a panic when > attempting to transmit frames on a mesh interface which > hadn't yet been put down. > > Signed-off-by: Thomas Pedersen <thomas@xxxxxxxxxxx> > --- > net/mac80211/mesh.c | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/net/mac80211/mesh.c b/net/mac80211/mesh.c > index eac9988..271ddc9 100644 > --- a/net/mac80211/mesh.c > +++ b/net/mac80211/mesh.c > @@ -993,6 +993,9 @@ void ieee80211_stop_mesh(struct ieee80211_sub_if_data *sdata) > struct beacon_data *bcn; > > netif_carrier_off(sdata->dev); > + if (sdata->dev->priv_flags & IFF_BRIDGE_PORT) > + /* stop bridge transmissions */ > + call_netdevice_notifiers(NETDEV_CHANGE, sdata->dev); Err, this seems like a really bad hack? I don't really think drivers should call that? johannes -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
