summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKirill Tkhai <ktkhai@virtuozzo.com>2018-03-19 14:39:05 +0300
committerDavid S. Miller <davem@davemloft.net>2018-03-22 18:11:29 +0300
commit1ae7762760736d4f7e4ea43e9ed03a608685c3d9 (patch)
tree8e99e42370309af21b14a0c15d88e1cc036a76aa
parent454bfe97837a3e3a5a15b768f8293f228e0f2f06 (diff)
downloadlinux-1ae7762760736d4f7e4ea43e9ed03a608685c3d9.tar.xz
net: Convert can_pernet_ops
These pernet_operations create and destroy /proc entries and cancel per-net timer. Also, there are unneed iterations over empty list of net devices, since all net devices must be already moved to init_net or unregistered by default_device_ops. This already was mentioned here: https://marc.info/?l=linux-can&m=150169589119335&w=2 So, it looks safe to make them async. Signed-off-by: Kirill Tkhai <ktkhai@virtuozzo.com> Signed-off-by: David S. Miller <davem@davemloft.net>
-rw-r--r--net/can/af_can.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/net/can/af_can.c b/net/can/af_can.c
index 6da324550eec..e899970398a1 100644
--- a/net/can/af_can.c
+++ b/net/can/af_can.c
@@ -954,6 +954,7 @@ static struct notifier_block can_netdev_notifier __read_mostly = {
static struct pernet_operations can_pernet_ops __read_mostly = {
.init = can_pernet_init,
.exit = can_pernet_exit,
+ .async = true,
};
static __init int can_init(void)