Re: [Patch net v2] ipv6: reorder ip6_route_dev_notifier after ipv6_dev_notf

2017-05-08 Thread David Miller
From: David Ahern Date: Thu, 4 May 2017 13:41:15 -0600 > On 5/4/17 11:36 AM, Cong Wang wrote: >> For each netns (except init_net), we initialize its null entry >> in 3 places: >> >> 1) The template itself, as we use kmemdup() >> 2) Code around dst_init_metrics() in ip6_route_net_init() >> 3) ip6

Re: [Patch net v2] ipv6: reorder ip6_route_dev_notifier after ipv6_dev_notf

2017-05-04 Thread David Ahern
On 5/4/17 11:36 AM, Cong Wang wrote: > For each netns (except init_net), we initialize its null entry > in 3 places: > > 1) The template itself, as we use kmemdup() > 2) Code around dst_init_metrics() in ip6_route_net_init() > 3) ip6_route_dev_notify(), which is supposed to initialize it after >

[Patch net v2] ipv6: reorder ip6_route_dev_notifier after ipv6_dev_notf

2017-05-04 Thread Cong Wang
For each netns (except init_net), we initialize its null entry in 3 places: 1) The template itself, as we use kmemdup() 2) Code around dst_init_metrics() in ip6_route_net_init() 3) ip6_route_dev_notify(), which is supposed to initialize it after loopback registers Unfortunately the last one st