Re: [PATCH net] vxlan: test dev->flags & IFF_UP before calling netif_rx()

2019-02-11 Thread David Miller
From: Eric Dumazet Date: Thu, 7 Feb 2019 12:27:38 -0800 > netif_rx() must be called under a strict contract. > > At device dismantle phase, core networking clears IFF_UP > and flush_all_backlogs() is called after rcu grace period > to make sure no incoming packet might be in a cpu backlog > and

Re: [PATCH net] vxlan: test dev->flags & IFF_UP before calling netif_rx()

2019-02-07 Thread Eric Dumazet
On Thu, Feb 7, 2019 at 12:27 PM Eric Dumazet wrote: > > netif_rx() must be called under a strict contract. > > At device dismantle phase, core networking clears IFF_UP > and flush_all_backlogs() is called after rcu grace period > to make sure no incoming packet might be in a cpu backlog > and stil

[PATCH net] vxlan: test dev->flags & IFF_UP before calling netif_rx()

2019-02-07 Thread Eric Dumazet
netif_rx() must be called under a strict contract. At device dismantle phase, core networking clears IFF_UP and flush_all_backlogs() is called after rcu grace period to make sure no incoming packet might be in a cpu backlog and still referencing the device. Most drivers call netif_rx() from their