freebsd-dev/sys/dev/mlx4
Hans Petter Selasky 1866c98e64 Infiniband clients must be attached and detached in a specific order in ibcore.
Currently the linking order of the infiniband, IB, modules decide in which
order the clients are attached and detached. For example one IB client may
use resources from another IB client. This can lead to a potential deadlock
at shutdown. For example if the ipoib is unregistered after the ib_multicast
client is detached, then if ipoib is using multicast addresses a deadlock may
happen, because ib_multicast will wait for all its resources to be freed before
returning from the remove method.

Fix this by using module_xxx_order() instead of module_xxx().

Differential Revision:	https://reviews.freebsd.org/D23973
MFC after:		1 week
Sponsored by:		Mellanox Technologies
2020-07-06 08:50:11 +00:00
..
mlx4_core Infiniband clients must be attached and detached in a specific order in ibcore. 2020-07-06 08:50:11 +00:00
mlx4_en Infiniband clients must be attached and detached in a specific order in ibcore. 2020-07-06 08:50:11 +00:00
mlx4_ib Infiniband clients must be attached and detached in a specific order in ibcore. 2020-07-06 08:50:11 +00:00
cmd.h Update the mlx4 core and mlx4en(4) modules towards Linux v4.9. 2017-11-15 11:14:39 +00:00
cq.h sys/dev/mlx[45]: fix uses of 1 << 31 2018-01-12 06:36:44 +00:00
device.h mlx4: Add board identifier and firmware version to sysctl 2018-12-05 13:30:48 +00:00
doorbell.h
driver.h mlx4en: Add support for netdump. 2018-12-05 13:32:15 +00:00
qp.h sys/dev/mlx[45]: fix uses of 1 << 31 2018-01-12 06:36:44 +00:00
srq.h
stats.h Update the mlx4 core and mlx4en(4) modules towards Linux v4.9. 2017-11-15 11:14:39 +00:00