Re: [PATCH net-next] net: dsa: fix added_by_user switchdev notification

2018-05-10 Thread David Miller
From: Vivien Didelot Date: Tue, 8 May 2018 23:03:12 -0400 > Commit 161d82de1ff8 ("net: bridge: Notify about !added_by_user FDB > entries") causes the below oops when bringing up a slave interface, > because dsa_port_fdb_add is still scheduled, but with a

Re: [PATCH net-next] net: dsa: fix added_by_user switchdev notification

2018-05-09 Thread Nikolay Aleksandrov
On 09/05/18 06:03, Vivien Didelot wrote: Commit 161d82de1ff8 ("net: bridge: Notify about !added_by_user FDB entries") causes the below oops when bringing up a slave interface, because dsa_port_fdb_add is still scheduled, but with a NULL address. To fix this, keep the dsa_slave_switchdev_event

Re: [PATCH net-next] net: dsa: fix added_by_user switchdev notification

2018-05-09 Thread Petr Machata
Vivien Didelot writes: > @petr I expect the same issue with Rocker, but I haven't tested it. Yeah, pretty sure. Such an obvious bug, sorry about that :-/ I'll send a rocker patch later today. Thanks, Petr

[PATCH net-next] net: dsa: fix added_by_user switchdev notification

2018-05-08 Thread Vivien Didelot
Commit 161d82de1ff8 ("net: bridge: Notify about !added_by_user FDB entries") causes the below oops when bringing up a slave interface, because dsa_port_fdb_add is still scheduled, but with a NULL address. To fix this, keep the dsa_slave_switchdev_event function agnostic of the notified info