1
0
Files
linux/include/net
WANG Cong 242d3a49a2 ipv6: reorder ip6_route_dev_notifier after ipv6_dev_notf
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 still happens in a wrong order because
we expect to initialize net->ipv6.ip6_null_entry->rt6i_idev to
net->loopback_dev's idev, thus we have to do that after we add
idev to loopback. However, this notifier has priority == 0 same as
ipv6_dev_notf, and ipv6_dev_notf is registered after
ip6_route_dev_notifier so it is called actually after
ip6_route_dev_notifier. This is similar to commit 2f460933f5
("ipv6: initialize route null entry in addrconf_init()") which
fixes init_net.

Fix it by picking a smaller priority for ip6_route_dev_notifier.
Also, we have to release the refcnt accordingly when unregistering
loopback_dev because device exit functions are called before subsys
exit functions.

Acked-by: David Ahern <dsahern@gmail.com>
Tested-by: David Ahern <dsahern@gmail.com>
Signed-off-by: Cong Wang <xiyou.wangcong@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2017-05-08 17:31:24 -04:00
..
2017-01-12 04:01:17 -05:00
2017-04-05 10:15:20 +02:00
2017-04-24 12:35:56 -04:00
2017-02-07 13:07:46 -05:00
2016-06-27 15:06:17 -04:00
2016-07-08 12:20:57 +02:00
2016-04-25 16:44:27 -04:00
2016-04-25 16:44:27 -04:00
2016-06-09 23:41:03 -07:00
2016-02-16 20:21:48 -05:00
2017-04-14 10:06:42 +02:00
2017-04-03 19:04:48 -07:00
2016-05-20 18:03:16 -04:00
2016-04-27 22:48:25 -04:00
2017-02-03 15:16:45 -05:00
2017-04-13 13:19:48 -04:00
2016-08-17 19:36:23 -04:00
2016-10-03 02:00:22 -04:00
2016-10-04 02:11:51 -04:00
2017-04-12 13:59:21 -04:00
2016-07-08 12:20:57 +02:00
2016-03-23 22:09:58 -04:00
2017-02-17 12:08:05 -05:00
2016-12-25 17:21:22 +01:00
2017-01-09 16:07:41 -05:00
2016-05-03 16:08:14 -04:00
2015-10-26 22:24:22 -07:00