Don't create any threads before SI_SUB_INIT_IF in the LinuxKPI. Else

kthread_add() will assert it is called too soon. This fixes a startup
issue when COMPAT_LINUXKPI is in enabled the kernel configuration
file.

Reported by:		Michael Butler <imb@protected-networks.net>
MFC after:		1 week
Sponsored by:		Mellanox Technologies
This commit is contained in:
Hans Petter Selasky 2017-03-09 09:17:43 +00:00
parent aacbef6cc1
commit c23b6e238f

View File

@ -546,7 +546,7 @@ linux_work_init(void *arg)
system_power_efficient_wq = linux_system_short_wq;
system_unbound_wq = linux_system_short_wq;
}
SYSINIT(linux_work_init, SI_SUB_LOCK, SI_ORDER_SECOND, linux_work_init, NULL);
SYSINIT(linux_work_init, SI_SUB_INIT_IF, SI_ORDER_THIRD, linux_work_init, NULL);
static void
linux_work_uninit(void *arg)
@ -560,4 +560,4 @@ linux_work_uninit(void *arg)
system_power_efficient_wq = NULL;
system_unbound_wq = NULL;
}
SYSUNINIT(linux_work_uninit, SI_SUB_LOCK, SI_ORDER_SECOND, linux_work_uninit, NULL);
SYSUNINIT(linux_work_uninit, SI_SUB_INIT_IF, SI_ORDER_THIRD, linux_work_uninit, NULL);