summaryrefslogtreecommitdiffstats
path: root/crypto/essiv.c
diff options
context:
space:
mode:
authorZiyang Xuan <william.xuanziyang@huawei.com>2022-09-15 09:55:55 +0800
committerMarc Kleine-Budde <mkl@pengutronix.de>2022-09-23 13:53:02 +0200
commitedd1a7e42f1d2d09c5f79ecef05ae19dc669bf34 (patch)
tree2e8318214c8989c304c3364beaaab56bff0f49a6 /crypto/essiv.c
parentd05d9eb79d0cd0f7a978621b4a56a1f2db444f86 (diff)
downloadlinux-edd1a7e42f1d2d09c5f79ecef05ae19dc669bf34.tar.gz
linux-edd1a7e42f1d2d09c5f79ecef05ae19dc669bf34.tar.bz2
linux-edd1a7e42f1d2d09c5f79ecef05ae19dc669bf34.zip
can: bcm: registration process optimization in bcm_module_init()
Now, register_netdevice_notifier() and register_pernet_subsys() are both after can_proto_register(). It can create CAN_BCM socket and process socket once can_proto_register() successfully, so it is possible missing notifier event or proc node creation because notifier or bcm proc directory is not registered or created yet. Although this is a low probability scenario, it is not impossible. Move register_pernet_subsys() and register_netdevice_notifier() to the front of can_proto_register(). In addition, register_pernet_subsys() and register_netdevice_notifier() may fail, check their results are necessary. Signed-off-by: Ziyang Xuan <william.xuanziyang@huawei.com> Link: https://lore.kernel.org/all/823cff0ebec33fa9389eeaf8b8ded3217c32cb38.1663206163.git.william.xuanziyang@huawei.com Acked-by: Oliver Hartkopp <socketcan@hartkopp.net> Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
Diffstat (limited to 'crypto/essiv.c')
0 files changed, 0 insertions, 0 deletions